TIBCO ActiveMatrix(R) BusinessWorks Service Engine 5.9.2 hotfix TIB_amx_3.1.2_hotfix001, is now available.
book
Article ID: KB0103709
calendar_today
Updated On:
Products
Versions
TIBCO ActiveMatrix BusinessWorks Service Engine
-
Not Applicable
-
Description
Description: You can download this HotFix from the TIBCO Product Support FTP server using your eSupport username and password, at
ftp://support-ftp.tibco.com
Once you have successfully logged into the server, you will find the hotfix packages under available_downloads/ActiveMatrix/BusinessWorksServiceEngine/5.9.2/TIB_amx_3.1.2_hotfix001
Listed below is a summary of updates included. Please refer to the hot fix readme document for any additional information.
================================================================================ Closed Issues in TIB_amx_3.1.2_hotfix001 (This Release)
TAP-7830 Administrator no longer adds an extra "/" to a SOAP endpoint URI whenever a a SOAP binding is created or edited.
TAP-7781 When an application with an outgoing reference is upgraded, the mapping of the binding to the node is no longer lost. When the application is deployed, the endpoints for the reference are no longer removed.
TAP-7764 Application upgrade now works when WSDL definition of a service provider is changed but the service name is not changed.
SDS-5033 Exporting a custom feature as DAA no longer fails with the exception "The feature xxxxxxx.feature was not resolved and is required for packaging".
SDS-5023 Business Studio now allows you to set the 'replyTo' property of an inbound destination
MED-2618 A JDBC connection leak exception is no longer thrown during initialization when the JDBC property of a Mediation flow with a QueryDB task is read.
CL-1992 When there are more than 100k logrecords in the logservice database, the node that runs logservice no longer goes out of memory with default heap size setting when the logservice is restarted.
CL-1981 When using the Log Viewer you are now able to run queries after exporting log entries.
BJMS-810 A JMS reference with an In-only operation without any part in the input message, and XMLBytes as Message Type no longer creates an incorrect JMS message type in the reference queue
BJMS-804 When reference with a JMS binding is configured with fixed-reply queue (for in-out MEP), the request message now sends the correlation ID that has been set in in the context of the request message.
AMRP-3218 A TIBCO Host instance now requires all nodes to be running when you perform an action to secure the communication to its nodes. If any of the nodes is not running, the action will return an error without making any changes.