TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix-03 is available.

TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix-03 is available.

book

Article ID: KB0102679

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

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.2.2/hotfix-03 to download the fix.

================================================================================
Closed Issues in 6.2.2_HF-003 (This Release)

AMBW-19975
After the TIBCO Enterprise Messaging Service (EMS) server was restarted, the Get JMS activity threw the error "javax.jms.IllegalStateException: Trying to Reconnect to JMS Server", and messages were not being processed until ActiveMatrix BusinessWorks 6.x was restarted. This has been fixed.

AMBW-20159
The password parameter for EMS could not be updated in the bwagent_db.json file with the key "emsuserpassword". This has been fixed.

AMBW-20251
The JDBCUpdate activity was wrongly committing changes to the database when the batch update option was used and the activity was inside a transaction group, and the transaction failed. This has been fixed.

AMBW-20410
The engine hangs if a response is not received during a Namespace lookup. This has been fixed.

AMBW-20453
The XSD element "Include" did not work with a chameleon schema. This has been fixed.

AMBW-20494
In TIBCO ActiveMatrix BusinessWorks 6.x, a stack overflow error was thrown at runtime if the JMS Receiver activity was using XSD elements from MDM. This has been fixed.

AMBW-20496
If the Concrete WSDL referred to a schema that contained a complex type and an element that were using the same name, only one of these was included in the Concrete WSDL. This has been fixed.

AMBW-20500
An exception was thrown when XSD and WSDL schemas that were used to connect to SalesForce were not resolved during design-time validation. This has been fixed.

AMBW-20566
When a JMS request reply activity was executing, the exception "Invalid temporary destination" was intermittently thrown. This has been fixed.

AMBW-20580
If bwagent was configured to use an external database and EMS for data persistence and transport, bwagent would remain in the "Unreachable" state if the EMS server was restarted. This has been fixed.
 
AMBW-20589
bwagent could not be configured to use SSL when connecting to an EMS server. This has been fixed.

AMBW-20590
If a WSDL contained nested schemas, an exception was thrown and the application failed to start. This has been fixed.
 
AMBW-20592
When using EMS and database as transport and persistence for bwagent, a large number of temporary queues were being created, but were being not cleaned up. This has been fixed.

AMBW-20696
When an application contained multiple JMS receiver activities, and the connection to the EMS server was reset, some JMS receiver activities did not receive messages. This has been fixed.

AMBW-20699
A memory leak was observed when the XSLT processor encountered schema imports inside an XSLT transformation. This has been fixed.

AMBW-20702
When configuring bwagent to use Oracle for data persistence and EMS for data transport, the driver that was required was called “oracle.jdbc.driver.OracleDriver”. When configuring bwagent
with other ActiveMatrix BusinessWorks components, a different Oracle driver, “oracle.jdbc.OracleDriver”, was required. This has been fixed.

AMBW-20758
BusinessWorks application failed with the error "no xsd for this imported location" when an importing schema contained a targetNamespace that does not exist in a formerly imported schema. This has been fixed. 

AMBW-20931
If Authorization was enabled for the EMS server, and the obfuscated password was set in the bwagent.ini file, bwagent was not able to connect to the EMS server. This has been fixed.

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

Issue/Introduction

TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix-03 is available.

Environment

TIBCO ActiveMatrix BusinessWorks 6.2.2

Attachments

TIBCO ActiveMatrix BusinessWorks 6.2.2 Hotfix-03 is available. get_app