TIBCO ActiveSpaces 2.1.2 hotfix-03 is now available.

TIBCO ActiveSpaces 2.1.2 hotfix-03 is now available.

book

Article ID: KB0104927

calendar_today

Updated On:

Products Versions
TIBCO ActiveSpaces -
Not Applicable -

Description

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.1.2/hotfix-03/ to download the hotfix.
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.2_HF-003 (This Release)
======================================
AS-2448 Crash observed at non-discovery nodes when network is disabled

AS-2441 Help output of as-admin (create a space with is_routed true flag) should show space is routed

AS-2426 Intermittent protocol timeout for put when it is done immediately after getSpace as leech role

AS-2425 ActiveSpaces crashes while handling arbitrarily long queries.

AS-2413 Remote client crases if getSpace is called without defining the space.

AS-2407 Boolean indication of partial or full result for a query with limit can now be checked
by using the Browser.isPartial() method.  The method returns TRUE if a full
result was returned and returns FALSE if a partial result was returned.

AS-2405 Return the count for a query result set through the Browser.size() method. Not supported for
timescope CURRENT, returns -1. Best effort for timescope NEW, and ALL.

AS-2402 Socket leak when continuous joins/leaves occur.

AS-2375 Using C API when eviction happens event type is expire instead of evict

AS-2354 Add a QueryLimit for the SpaceDef, and allow BrowserDef/ListenerDef/EventBrowserDef to
overwrite it by calling setQueryLimit.

AS-2316 As-admin stats for query count does not increase when a timescope CURRENT browser is created

AS-2245 Need option not to delete old Shared-Nothing files after recovery completes

AS-2228 ASMM not supporting secure metaspace connection.

The syntax for the startupMetaspaces server property now supports a secure
connection by using token values (where the tokens 3, 4, 5, 6 are new).

   Example: {"ms","discovery", "listen", "security token file", "domain", "username", "password"}
  - token 0 = metaspace name
  - token 1 = discovery url
  - token 2 = listen url
  - token 3 = security token file path
  - token 4 = domain
  - token 5 = user name
  - token 6 = password (if obfuscated: starts with OBF: enabled by the Jetty
    password utility).

This can take the form of one of the three possible combinations:

  - Token 0, 1, 2 : The classic case, which includes metaspace name + discovery URL
    + listen URL.
  - Token 0, 1, 2, 3 : Includes the tokens in the classic case plus the security token
    file path (where user authentication is not required).
  - Token 0, 1, 2, 3, 4, 5, 6 : Every token is needed.

Token 6 has two forms:

  - Clear text password, OR
  - Obfuscated password enabled by the Jetty utilty and which starts with "OBF:"

To obfuscate the password, enter the following command:

java -cp jetty-6.1.26.jar:jetty-util-6.1.26.jar org.mortbay.jetty.security. Password
&ltpassword>

If the input &ltpassword> is obfuscated (i.e.,Starts with "OBF:"), this makes the password
unobfuscated.  The JAR file is located in the asmm/lib folder.

=================================================================================

Issue/Introduction

TIBCO ActiveSpaces 2.1.2 hotfix-03 is now available.

Environment

Product: TIBCO ActiveSpaces Version: 2.1.2 OS: --------------------