Description of problem:
Description from the customer
" In our environment Tibco JMS connection factory objects are stored in LDAP, so to make JMS connections from application deployed on JBoss we configured external JNDI for LDAP lookup and connection factory objects are mapped to local JNDI using Simple Naming alias configuration. We are able to lookup & connect to Tibco JMS queues, but connection pool is not created by JBoss container. As per the case notes it is not supported in JBoss EAP since we are doing external JNDI lookup for connection factory objects and then making JMS connections.
In the existing environment (Websphere/WebLogic) connection pool is being created by container for the same setup, so it is a migration show stopper for us from Websphere/WebLogic to JBoss, since each application needs to go through code update for custom connection pooler."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
They are using EAP cartridge in OpenShift Enterprise.
Are there any alternate solutions as an interim solution ?
for Websphere MQ they must use resource adapter from IBM. There is documentation how to do this in .
Please have a look at https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html/Administration_and_Configuration_Guide/Configure_a_Generic_JMS_Resource_Adapter_for_Use_with_a_Third-party_JMS_Provider.html to use the Generic JMS RA adapter and specify JNDI parameters.
In that case, you would pass all the JNDI parameters in the JndiParameters <config-property> element.