WebSphere Extended Deployment messages
Operating Systems: All supported


PROX5003W

WARNING_NO_CURRENT_JNDINAME=PROX5003W: There is no DataSource JNDI name set on the current thread local storage when using the proxy datasource. The JNDI name specified in the jndiNames custom property of the proxy DataSource will be used. This is normal for transaction recovery, but it should not happen during the normal CMP EJB invocations.

Explanation

This problem happens when the proxy DataSource is accessed while there is no DataSource JNDI name set on the thread local storage. The JNDI name specified in the jndiNames custom property of the proxy DataSource will be used.

User response

If the warning message occurs on the transaction recovery thread, it is normal. In any other cases, users should inspect their applications to make sure the DataSource JNDI name is set to the thread local storage for every transaction.

Terms of Use | Feedback