[ https://issues.jboss.org/browse/WFLY-5213?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-5213: ----------------------------------- I'm not sure this is a correct use case. If you specify the org.wildfly.extension.messaging-activemq module, the code that injects JMSContext will do a JNDI lookup to locate the TransactionSynchronizationRegistry *in Artemis JNDI*. As the code is written now, only the JNDI lookup for external resources (Artemis ConnectionFactory) must use external-context. What's the use case? If you really want to leverage org.wildfly.extension.messaging-activemq module, it is recommended to configure a pooled-connection-factory to connect to a remote Artemis broker as explained in https://docs.jboss.org/author/display/WFLY10/Connect+a+pooled-connection-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)