Products | Versions |
---|---|
TIBCO ActiveSpaces | - |
Not Applicable | - |
Description:
This hot fix can be downloaded from the TIBCO Support file transfer server- mft.tibco.com.
Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser: https://mft.tibco.com
FTP: port 21
SFTP: port 22
FTP using your browser is not supported, please use an FTP client or command-line. TIBCO employees must use a secure protocol.
Once logged on you can find the hot fix under " /AvailableDownloads/ActiveSpaces/2.1.5/hotfix-05/ "
This
.zip file also has the Readme file inside. Please unzip the file and
look for the Readme file for Instruction on how to apply the hotfix.
Closed Issues in 2.1.5_HF-05 (This Release)
=================================================================================
AS-3932 While authenticating a user, ActiveSpaces removed all spaces configured in the LDAP baseDN policy.
AS-3972 When attempting to lock a key as a remote client and the lock wait expired, the client crashed.
AS-3981 When recovering from Shared-Nothing Persistence using Fast Recovery, if the schema was altered as follows prior to the recovery, the seeders of the cluster could crash:
- by changing the order of the fields
- by adding a field in between existing fields
AS-3984 The remote client ignored the connect_timeout attribute. As a result, the metaspace.connect() method was blocked if a proxy was not available.
AS-3996 Recovery was not prevented resulting in missing data if you tried to recover from Shared-Nothing Persistence, before bringing up all the seeders required to recover the data.
AS-4001 If an index was added, a query on the 'char' field type did not return any results.
AS-4002 A problem with redistribution sometimes caused duplicate entries.
AS-4004 When calling Browser.next(), sometimes the call failed with an Operation Timeout exception even if there were tuples remaining to be returned.
AS-4008 When calling getSpace() from multiple threads at the same time, sometimes one calling thread became unresponsive.
=================================================================================