Resolution:
When JNDI lookup is enabled with JMS authentication turned on, TIBCO Adapters built using C++ SDK APIs failed to start. This was fixed on all the platforms supported by the adapter.

Symptoms
=========
Custom adapter is configured with JMS transport. When the Authentication parameter in tibemsd.conf is enabled and JNDI Lookups in repo configuration is checked, if the user name is created with password, custom adapter can not connect to the EMS server even if the correct password is provided in repo configuration in designer.
This is applicable for the following adapters:

> TIBCO Adapter for Active Database
> TIBCO Adapter for R/3
> TIBCO Adapter for Teradata
> TIBCO Adapter for MQSeries
> TIBCO Adapter for LDAP
> TIBCO Adapter for COM
> TIBCO Adapter for File
> TIBCO Adapter for CORBA
> TIBCO Adapter for Remedy
> TIBCO Adapter for Tuxedo
> Custom Adapters using C++ TIBCO Adapter SDK APIs.

Cause
=========
Password not being sent to underline EMS api's correctly while creating jms connection.

WorkAround
=========

Refer to resolution.

Resolution
=========
The issue at run time has been fixed in TIBCO Adapter SDK 5.4.0 hotfix 2 and TIBCO Adapter SDK 5.4.1 hotfix 2.

This fix is applicable for the following list of adapters:

> TIBCO Adapter for Active Database
> TIBCO Adapter for R/3
> TIBCO Adapter for Teradata
> TIBCO Adapter for MQSeries
> TIBCO Adapter for LDAP
> TIBCO Adapter for COM
> TIBCO Adapter for File
> TIBCO Adapter for Peoplesoft.
> TIBCO Adapter for CORBA
> TIBCO Adapter for Remedy
> TIBCO Adapter for Tuxedo
> Custom Adapters using C++ TIBCO Adapter SDK APIs.

Note
=====
Please refer to LBN LBN1-8Z6629 for the news related to using JNDI during design time.

For all TIBCO Adapters using C++ SDK APIs (with JNDI lookup) and JMS/EMS authentication enabled, the adapter failed to connect to the EMS server at run time.