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-06/ 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-06 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 06 are:
=================================================================================
Closed Issues in 2.0.2_HF-006 (This Release)
AS-2415
In a "split-brain" situation, heartbeat signals could not detect a cluster isolation
condition based on a fixed timeout interval. This issue has been resolved.
AS-2478
The as-admin Java command line did not accept connection parameters inline.
The as-admin nows accepts an inline <admin_command>, which can be a connect statement
in this case. The inline parameters must be preceded by "-s" -- for example,
java -jar as-admin.jar -i spacedefs.txt -s ?connect name <msname>
discovery <tibpgm://> listen <tcp://>
AS-2423
When starting multiple BusinessEvents engines at the same time, one of the BusinessEvents
engines acquired the ActiveSpaces lock, which was never released and caused the other
BusinessEvents engines to hang.
AS-2494
When performing recovery of a space from shared-nothing persistence files, a run-time
crash could be observed on one or more seeder nodes. This issue has been resolved.
AS-2495
After performing recovery of a space from shared-nothing persistence files, memory
usage of the seeder nodes is more than what it was prior to failure.
=================================================================================