Description:
You can download this HotFix from the TIBCO Product Support ftp server, mft.tibco.com. You will need to provide your TSC (TIBCO Support Central) credentials. Your username is your email address to access the server.

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 you have successfully logged into the server, go to /AvailableDownloads/BusinessWorks/6.3.1/hotfix-01 to download the fix.

================================================================================
Closed Issues in 6.3.1_HF-001(This Release)
AMBW-20428
When using SOAP over JMS binding with TIBCO EMS Explicit Client or Client Acknowledgement mode, the SOAP binding incorrectly confirmed the message even if the job threw an error. This has been fixed.

AMBW-21845
When an AppSpace contained an application process using a “Wait for JMS Message” activity, and the ActiveMatrix BusinessWorks engine persistence mode is configured datastore, the error message “Error deserializing WSDLMessagePart” is thrown. This has been fixed.

AMBW-21939
A session leak has been fixed on the “JMS Connection” Shared Resource. This has been fixed.

AMBW-22189
The "JMS Receiver" activity incorrectly continued to create jobs even after the EMS Server was terminated. This has been fixed.

AMBW-22204
TIBCO ActiveMatrix BusinessWorks published SOAP/JMS service response messages in PERSISTENT mode, even if the request message has been published by the consumer in NON_PERSISTENT mode. This has been fixed.

AMBW-22308
The REST wizard crashed in Business Studio during the validation of recursive schema references for REST binding. This has been fixed.

AMBW-22381
When importing dependent schemas, schema references were not always properly resolved. This has been fixed.

AMBW-22413
An error was thrown if the output parameter of the data type in the "JDBC Call Procedure" activity was set to “Null”, or left empty. This has been fixed.

AMBW-22456
The "JMS Receiver" activity incorrectly continued to create jobs even after the EMS Server was terminated. This has been fixed.

AMBW-22493
The AppNode status hung if an application used JDK 1.7, or later versions of the software, and allowed unsynchronized access from multiple threads. This has been fixed.

AMBW-22501
JDBC activities did not free temp tablespace when working with Oracle LOB data. This has been fixed.

AMBW-22502
Applications deployed in a single AppNode stopped consuming JMS inbound messages under load. This has been fixed.

AMBW-22506
The TIBCO ActiveMatix BusinessWorks 6.3.1 HTTP client did not support for TLSv1.2 GCM ciphers offered in Java 8. This has been fixed.

AMBW-22569
TIBCO ActiveMatrix BusinessWorks 6.3.x did not provide a configuration field to set the delivery mode for response messages in JMS bounded SOAP Services. This field has been added.
 
AMBW-22592
A WS-Security exception was thrown when SOAP messages encrypted using AES-GCM (AES/GCM/NoPadding) were decrypted.

AMBW-22647
EAR files could not be generated from Business Studio if they included SVG process diagrams to show in the Admin UI. This has been fixed.

AMBW-22680
The cache did not properly resolve when the bwdesign export command was used for complex projects. This has been fixed.

AMBW-22746
When executing the bwdesign import command to import commands,  the exception “resource tree locked exception” was thrown. This has been fixed.

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