ExtremeZ-IP Hot Fix Release History - Version 3.1
Version 3.1 releases are downloaded as either standalone hot fixes or full installer packages. Every installer is cumulative and includes all updates from previous versions.
To install a full installer release:
- After unzipping the downloaded file, you will be presented with an executable installer.
- Run the installer and your ExtremeZ-IP installation will be updated and all settings will be retained.
To install a standalone hot fix release:
- Extract the downloaded components from the zip file.
- Stop the ExtremeZ-IP Service.
- Close the ExtremeZ-IP Administrator if it is open.
- Replace your files with those in the zip file.
- Launch ExtremeZ-IP Administrator.exe.
Note: A 3.1 hot fix can only be applied to version 3.1 installations. If you are running a version previous to 3.1, be sure to download and install a full installer version before installing a standalone hot fix version.
ExtremeZ-IP 3.1.2x30 - Download Now - Standalone Hot Fix
- New Registry key 'DebugLogThrowThreadException' for testing whether Dr. Watson crash logging is configured.
- New Registry key 'DebugLogCloseHandle' added for enhanced debug logging on CloseHandle calls.
ExtremeZ-IP 3.1.2x25 - Download Now - Standalone Hot Fix
- When 'RenameLogAtStartup' and 'UseCriticalSectionMonitor' are both enabled, if the server hangs, a copy of the debug log will be made automatically at 30 seconds, 2 minutes and 10 minutes after the hang is detected.
ExtremeZ-IP 3.1.2x21 - Download Now - Standalone Hot Fix
- CPU usage (average / current) Memory Usage: (RAM/ virtual/ current load) added to Date line in debug log.
- Date, time and minute log entry added to the debug log on a per-minute basis.
- New registry key 'RenameLogAtStartup' added so that clients will automatically get a log ready to send to Group Logic after restarting the server.
ExtremeZ-IP 3.1.2x18 - Download Now - Standalone Hot Fix
- Added code to log when processing large folder hierarchies (dropped in an ExtremeZ-IP volume from the Windows server) takes a long time.
- Added more logging for tracking notification processing.
- Added new registry key for tracking what portions of the code have executed.
- Added different critical section logging registry key "CriticalSectionMonitorLogFrequencyInMilliseconds", so that we have finer control of granularity.
- Added support for logging of volume enumeration.
- Enhanced critical section monitor to provide information about whether a thread is stuck inside a critical section, or is stuck waiting on a critical section.