TIBCO ActiveMatrix(R) Service Bus 3.1.5 Hotfix, TIB_amx_3.1.5

Products	Versions
TIBCO ActiveMatrix Service Bus	-
Not Applicable	-

Description

Description:

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

Introduction

Hotfixes are cumulative. This hotfix includes all previous generally available

hotfixes for TIBCO ActiveMatrix(R) Platform 3.1.5.

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

Closed Issues in 3.1.5_hotfix014 (This Release)

This hotfix contain fixes that apply to the following types of installations:

- Administration

- Runtime Host

AMRP-4765, AMRP-4817

Stopping of a TIBCO ActiveMatrix node no longer hangs due to the transaction

manager perpetually waiting for the Flush Manager thread to complete.

AMRP-4783

A node restart is no longer required to recover in-doubt transactions performed

by TIBCO ActiveMatrix BPM applications. Instead, the transaction manager now

automatically resolves in-doubt transactions every five minutes (default) while

the node is running.

In-doubt transactions are caused typically when a connection to a database or

TIBCO Enterprise Messaging Server (EMS) is lost intermittently. The transaction

manager periodically looks for in-doubt transactions and tries to resolve them,

provided the connection was restored.

To change the default interval for automatic transaction recovery add this line

to the tibamx_<node>.tra file (or add the system property for your nodes from

TIBCO ActiveMatrix Administrator) java.property.amf.node.tx.periodicrecoveryenabled=<time in minutes>

NOTE: When using Microsoft SQL Server, we strongly recommend setting a node level

transaction timeout. Microsoft SQL Server has been found to not roll back active

transactions started by clients whose JDBC connection gets disconnected after beginning

the transaction, but before the 'prepare' phase. Such active transactions can remain

in the system indefinitely and disrupt normal TIBCO ActiveMatrix BPM functionality.

To set the overall transaction time out on the node, add this line to the

tibamx_<node>.tra file (or add the system property for your nodes from

TIBCO ActiveMatrix Administrator) java.property.amf.node.txtimeout=<value in seconds>

Example:

java.property.amf.node.txtimeout=600

(a 10-minute timeout)

DSS-877

An SSL-enabled HTTP connector no longer prompts the client for mutual authentication

during an SSL handshake when not configured to require mutual authentication.

TAP-13044

Deploying an TIBCO ActiveMatrix BPM application a second time after an earlier upgrade failure

that was not cleaned up using force undeploy no longer prematurely removes the endpoints

of the older version. Instead, users see a validation error, and the second deploy action

is blocked. The error message is as follows:

"Not allowed to deploy the version '<new version>' of application '<app name>'.

This version may have failed to deploy earlier, and if so it should be force undeployed first."

Note that force undeploy destroys BPM data for a given version, which means all existing

work items and process instances of the current version are cancelled. Force undeploy must be

used only when you are sure that the BPM data for the version you are force undeploying

is not needed and its loss is acceptable. Otherwise, contact TIBCO Support.

TAP-13102

This covers an alternate scenario of TAP-13044. In the following scenario applicable

to TIBCO ActiveMatrix BPM user applications, the endpoints of the old version of your

application are no longer prematurely removed:

1. Version 'v1' of your application is deployed.

2. You attempt to upgrade it to version 'v2' but the deployment fails.

3. You force-undeploy 'v2', but while force-undeploy is in progress, you go to the next

step without waiting for the force-undeploy to complete.

4. You switch the current version of your application to 'v1', but don't deploy.

5. You switch the current version of your application to 'v3', and deploy. At this point,

you will see a validation error that prevents the deployment. This avoids the

issue that caused endpoints of your old version 'v1' to be prematurely removed.

TAP-13110

The Component Status and Binding Status panels in TIBCO ActiveMatrix Administrator UI

under Application details screen are now optimized and render faster.

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

NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.

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

TIBCO ActiveMatrix(R) Service Bus 3.1.5 Hotfix, TIB_amx_3.1.5_hotfix014 can be downloaded from the TIBCO Product Support file transfer server,

mft.tibco.com, using your username and password for the TIBCO Support Central website. Please note you should use an FTP or SFTP client or command-line FTP.

TIBCO employees must use a secure protocol.

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

Once logged on you can find the hotfix under:

available_downloads/ActiveMatrix/ActiveMatrixServiceBus/3.1.5/TIB_amx_3.1.5_hotfix014

Issue/Introduction

TIBCO ActiveMatrix(R) Service Bus 3.1.5 Hotfix, TIB_amx_3.1.5_hotfix014, is now available.

Environment

Applicable Products This hotfix applies to the following products and versions: - TIBCO ActiveMatrix Service Bus 3.1.5 - TIBCO ActiveMatrix Service Grid 3.1.5 - TIBCO ActiveMatrix BPM 1.3.X, 2.0.0, 2.1.0 - TIBCO Business Studio BPM Edition 3.5.3, 3.5.5, 3.5.10, 3.5.20 - TIBCO ActiveMatrix BusinessWorks Service Engine 5.9.3 + HF-006 or above (5.9.3-HF-006 or above is mandatory for use with this hotfix)

Additional Information

TIB_amx_3.1.5_hotfix014_readme.txt

Welcome to "KB Articles"