[
https://issues.jboss.org/browse/WFLY-5213?page=com.atlassian.jira.plugin....
]
Bartosz Andrzejewski edited comment on WFLY-5213 at 10/14/16 4:06 AM:
----------------------------------------------------------------------
Hello [~jmesnil],
I did it the same way you described, with one difference:
I'm using latest WildFly 10.1.0 and while configuring external-context I used
"org.wildfly.extension.messaging-activemq" module, where i configured all the
connectors.
It seems that JMS Context and Queue is injecting, but while I'm trying to use Context
there is runtime exception (NameNotFoundException) - looking for
comp/TransactionSynchronizationRegistry.
Any idea what that could be ? I would really appreciate any clues(I already spend few days
on that).
A bit of stacktrace:
...
Caused by: javax.naming.NameNotFoundException: comp/TransactionSynchronizationRegistry --
service jboss.naming.context.java.comp.TransactionSynchronizationRegistry
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:223)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at
org.wildfly.extension.messaging.activemq.deployment.injection.InjectedJMSContext.lookup(InjectedJMSContext.java:132)
... 74 more
was (Author: drzeyan):
Hello [~jmesnil],
I did it the same way you described, with one difference:
I'm using latest WildFly 10.1.0 and while configuring external-config I used
"org.wildfly.extension.messaging-activemq" module, where i configured all the
connectors.
It seems that JMS Context and Queue is injecting, but while I'm trying to use Context
there is runtime exception (NameNotFoundException) - looking for
comp/TransactionSynchronizationRegistry.
Any idea what that could be ? I would really appreciate any clues(I already spend few days
on that).
A bit of stacktrace:
...
Caused by: javax.naming.NameNotFoundException: comp/TransactionSynchronizationRegistry --
service jboss.naming.context.java.comp.TransactionSynchronizationRegistry
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:223)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at
org.wildfly.extension.messaging.activemq.deployment.injection.InjectedJMSContext.lookup(InjectedJMSContext.java:132)
... 74 more
Injecting external context to Artemis fails
-------------------------------------------
Key: WFLY-5213
URL:
https://issues.jboss.org/browse/WFLY-5213
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Beta2
Reporter: Ondřej Kalman
Assignee: Jeff Mesnil
Fix For: 10.0.0.CR1
When external-context is defined in EAP and it's pointing to external Artemis broker,
it can't be injected in to MDB via @Resource(lookup =
"java:global/externalcontext"). Such injection results in null object.
Injecting destinations from external context results in
javax.ejb.EJBTransactionRolledbackException.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)