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.0/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.

The defects fixed in TIBCO ActiveSpaces 2.0.0 Hotfix 01 are:


AS-909

Under certain circumstances, when using all members, when persisters were killed, the console would print an unnecessary protocol timeout warning, even  though the request had properly returned with an error. This issue has been fixed.


AS-911

Under certain circumstances, when using shared nothing persistence, protocol timeout messages were seen on the client. This issue has been fixed.


AS-1077

If the operating system did not have TCP keepalive enabled, connections between members would close after a long period of inactivity, causing a member to drop. This issue has been fixed.


AS-1079

Indexes were not returning correct results when composite indexes were used. This issue has been fixed.


AS-1080

Snapshot browsers were hanging indefinitely when many browsers were created over a short time frame in the Linux environment. This issue has been fixed.


AS-1081

During a transaction, when a seeder joined or left and caused a redistribution of tuples, the transaction state was not being redistributed correctly, causing an inconsistency of transaction state. This could cause the transaction to appear committed to clients reading the uncommitted changes. This issue has been fixed.


AS-1083

Browsers, event browsers, and listeners would sometimes miss some tuples or events related to them if the tuples were involved in a transaction. This issue has been fixed.


AS-1085

If a Take occurred within a transaction, the Take was being immediately committed instead of waiting for the commit or rollback. This issue has been fixed.


AS-1086

When recovering a space using shared-all persistence with replication, seeders would crash. This issue has been fixed.


AS-1088

A .Net client (peer or remote client) would sometimes cause seeders to crash if the space had a DateTime field. This issue has been fixed.


AS-1090

Using the .Net API with the 32-bit library would always throw an exception on a metaspace connect. The .Net version of as-agent would error out. This issue has been fixed.


AS-1091

Calling Space.isReady() in the .Net API was causing a crash. This issue has been fixed.