Resolution:
Description:
============
When JNDI Context URL of a JMS Connection resource contains two EMS servers in FT like “tibjmsnaming://localhost:7222, tibjmsnaming://localhost:7224”, log entity like following can be seen in EMS log at BW engine startup.

****************
2010-03-30 14:47:52.239 [tibbw@lin312.cpwplc.net]: Disconnected,
connection id=3, reason: connection terminated (dconn.c:957)
****************

Environment:
===========
TIBCO Runtime Agent(TM): 5.5.4 (JMS_Version 4.4.3)
TIBCO ActiveMatrix BusinessWorks(TM): 5.6.3

Cause:
=====
It is an issue of EMS client library version 4.4.3 and can be reproduced with the following code fragment.

****************
String  providerContextFactory =
                            "com.tibco.tibjms.naming.TibjmsInitialContextFactory";
String  defaultProviderURLs =
                 "tibjmsnaming://localhost:7222, tibjmsnaming://localhost:7224";
Hashtable env = new Hashtable();
            env.put(Context.INITIAL_CONTEXT_FACTORY, providerContextFactory);
            env.put(Context.PROVIDER_URL, providerUrls);
QueueConnectionFactory queueFactory =
               (QueueConnectionFactory)jndiContext.lookup("FTQueueConnectionFactory");    
            QueueConnection queueConnection = queueFactory.createQueueConnection();
            QueueSession queueSession    = queueConnection.createQueueSession(false, 1);
            
            queueConnection.start();
            queueConnection.close();
****************

Resolution:
==========
The problem should be fixed in EMS client library version 5.1.3. TRA 5.6.2 includes that library and currently there is no officially supported procedure to upgrade the client library besides upgrading the whole TRA version.

This issue does not have any impact on BW functionality. Ignore the log entry if you do not have a TRA upgrade roadmap.