[jboss-jira] [JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries
[
https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi...
]
Jeff Mesnil commented on WFLY-13424:
------------------------------------
I don't understand why the order of entries is now significant. As long as the JMS
ConnectionFactory is properly bound in JNDI, it should be resolved by the `ee` subsystem
to provide the default JMS ConnectionFactory (whether it's a direct JNDI entry or an
alias)
External pooled connection factory won't be properly injected if
it has several JNDI entries
--------------------------------------------------------------------------------------------
Key: WFLY-13424
URL: https://issues.redhat.com/browse/WFLY-13424
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 19.1.0.Final
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Priority: Major
Fix For: 20.0.0.Beta1
If the default JNDI name for MDB to get the resource adapter is not the first entry of
the JNDI names bound for a pooled-connection-factory then the injection fails.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)