Products | Versions |
---|---|
TIBCO ActiveSpaces | - |
Not Applicable | - |
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-01/ 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.
Please note that with the 2.0.2 hotfix-01 release, the default setting for the as-admin Admin CLI command for defining fields with the define | create space command or altering a space with the alter space command is "not nullable." Previously, the default value was nullable. The default setting for defining or altering fields using ActiveSpaces API calls remains "not nullable."
The defects fixed in TIBCO ActiveSpaces 2.0.2 Hotfix 02 are:
Closed Issues in 2.0.2_HF-001 (This Release)
AS-1662
A datetime value in tuples caused the system to go down.
AS-1673
Data loss occurred with repeated space recovery.
AS-1675
The ActiveSpaces browser was not returning all data values.
AS-1690
Spaces remained in the READY state after a persister error occurred, causing creation of duplicate records.
AS-1692
Two entries were stored in the shared nothing file for puts when sharedd nothing persistence was used with transactions.
AS-1680
When an alter space operation was performed, a newly added index could be used before it was initialized fully.
AS-1775
ActiveSpaces sometimes crashed with share-nothing persistence if the same key was written at the same time via a batch or concurrent operation.
AS-1778
The invokeMember method crashed for a Java Native Interface (JNI) method and resulted in a stack trace being printed.
AS-1788
A memory leak was observed for the following API calls for ActiveSpaces 2.0.2:
- Metaspace.getSpaceDef
- Browser routines
- Metaspace.browse
- Space.browse
- Listener routines
- Metaspace.listen
- Space.listen
The memory growth was slow but happened each time one of these methods was called. As-admin was using a browser to retrieve statistics, so the issue also applied to as-admin statistics.