Description:
Symptoms
========
The adapter will not failover to the next Tuxedo Server when WSNADDR is specified as an FT pair, using comma seperated values.

Impact
======
Loss of Functionality
The adapter has to be restarted.


Cause
=====
The root cause of the problem is that the adapter does not reconnect to the Tuxedo server, when the Tuxedo server is stopped and started during the idle time of the adapter.
Workaround
==========
None

Resolution
==========
Upgrade to TIBCO Adapter for Tuxedo5.3.0 Hotfix 1 or above version to resolve this issue.

The variable WSNADDR needs to be set as shown below:
tibco.env.WSNADDR //&ltmachine1>:&ltport>,//&ltmachine2>:&ltport>

--> When both the services are running, adapter starts up and processes messages with services on the first machine.
--> When one of the services is brought down, on the first request adapter goes into reconnection and connects to the available services and processes further requests.
--> This feature is avaiable for all versions from adtuxedo 5.3.0 HF 1.
--> This feature is not available in the GAed version of adtuxedo 5.3.0.
Symptoms:

Cause: