Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveSpaces/2.0.2/hotfix-02/ to download the hotfix.
This .tar file also has the Readme file inside. Please untar the file and look for the Readme file for Instruction on how to apply the hotfix.


IMPORTANT NOTE: To uninstall ActiveSpaces 2.0.2 hotfixes, you must first uninstall ActiveSpaces 2.0.2 Hotfix 2, and then uninstall ActiveSpaces 2.0.2 Hotfix 1.  Do not select both hotfixes for uninstallation at the same time.
Introduction: Hotfixes are cumulative. This is the second hotfix for TIBCO ActiveSpaces 2.0.2.


The defects fixed in TIBCO ActiveSpaces 2.0.2 Hotfix 02 are:


AS-1736

When a client doing transaction left before committing, rollback did not happen; this occasionally causied entries to be in an inconsistent state


AS-1741

With shared-nothing persistence, when capacity was set with LRU eviction, and multiple puts were done in a transaction, when the transaction was committed, evictions did not occur for some of the operations.


AS-1809

With shared-nothing persistence and eviction policy set, when puts were done on keys already present, the statistics reported for "Entries" exceeded the number of entries.


AS-1828

With shared-nothing persistence, a JVM crash was observed when recovering bigger files.


AS-1862

Using a secondary hash index caused ActiveSpaces to crash.


AS-1890

When a tuple returned from onRead had null values for some space fields (including field types String, DateTime, or Blob), this caused operations (for example, get, take and put) to hang.  


AS-1893

If a runtime exception was thrown from an onRead persister callback, it caused operations (for example, get, take, and put operations) to hang.


AS-1922

The Alter Space operation allowed setting of spaceDef attributes, causing a system crash. This issue has been resolved.


AS-1992

Shared Nothing file size grew due to fragmentation.


AS-2023

Crash fixes in PGM routines were implemented, resulting in improvement instability.