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)
================================================================================ Closed Issues in 3.1.5_hotfix011 (This Release)
AMRP-4605 Undeploying and deleting TIBCO ActiveMatrix BPM user applications no longer occasionally fails due to a low-level provisioning error.
AMRP-4625 The describeHost command (used with the tibcohost executable) no longer returns the incorrect hotfix version, which only occurred in some cases.
MED-3275 For a one-way MEP operation, invoke tasks on the fault path no longer fail, and tasks after the invoke task are now processed.
PER-1745 Requests that contain unsigned SAML tokens with a signed X509 certificate are no longer authenticated as signed SAML tokens.
TAP-12136 When deploying an upgraded TIBCO ActiveMatrix BPM user application, the upgrade will not change the state of existing versions until the new version is successfully upgraded. This ensures that if a failure happens during deployment of an upgraded application it does not change the state of the previous version that was running.
TAP-12256 During deployments after an application has been upgraded, the CLI no longer returns prematurely while there are still pending tasks for the new version.
TAP-12257 When deploying several applications together, applications are deployed serially according to the application’s components’ dependencies. This prevents applications from missing dependencies, which causes TIBCO Administrator to get into an inconsistent state.
TAP-12289 Connections now are restored correctly when TIBCO Enterprise Message Service is shut down and restarted in replicated Administrator environments.
TAP-12313 The ActiveMatrix Administrator no longer enters an inconsistent state when deployment fails during application upgrades. In the event of a deployment failure users will now be able to force undeploy the failed deployment and go back to a state prior to the deployment failure.