Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.
Closed Issues in 5.3.3 Hotfix 5 (This Release)
CR: BC-7359
When using Microsoft SQL Driver 2008 Database for runtime with Native Microsoft JDBC Driver (sqljdbc4.jar), transactions that have been processed earlier by TIBCO BusinessConnect(tm) engine could not be resent due to an error in the way the transactions are marked for resent. This issue is fixed.
CR: BC-7358
TIBCO BusinessConnect engine that embeds the SSH Client was not able to handle certain exceptions that are being thrown by the library. This resulted in improper error handling. This issue is fixed with appropriate error handling.
CR: BC-7261
TIBCO BusinessConnect engine that embeds the SSH Client was not able to handle SSH exceptions that were thrown with 500 error code. This resulted in improper error handling. This issue is fixed with appropriate error handling.
CR: BC-7421
TIBCO BusinessConnect engine that embeds the SSH Client was not able to throw appropriate error when the SSH cache tunnel timeout expires to re-establish the SSH tunnel connection. This results in files being left out after the timeout period has passed. This issue is fixed by throwing the exception and re-establishing a new SSH Tunnel.
CR: BC-7423
TIBCO BusinessConnect credential alerter uses a default smtp 'from' address when sending alerts. BusinessConnect alerter should also be able to use authentication when the smtp server requires it. This fix requires a property
, which should be added to every interior BusinessConnect engine's tra file, which may be running the alerter. The value of the property must be a valid smtp address, e.g. alerter@company.com. The alerter will use smtp authentication, if the configured outgoing smtp proxy server entry has been setup with a username and password.
Issue/Introduction
TIBCO BusinessConnect 5.3.3 hotfix 5 has been released.
Environment
Product: TIBCO BusinessConnect
Version: 5.3.3
OS: All
--------------------