2:39 p.m.
Not all CDI scopes available to MDB's
-------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 7.1.0.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 p.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas updated AS7-3107:
--------------------------------
Summary: CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
(was: Not all CDI scopes available to MDB's)
Fix Version/s: (was: 7.1.0.Final)
Description:
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:37 p.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas updated AS7-3107:
--------------------------------
Component/s: JMS
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-3107:
----------------------------------
do you have a test case to reproduce this issue?
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:59 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-3107:
----------------------------------
BTW, I am not sure to understand what you're saying:
I found out that MDBs work great - request and app contexts are
active during message delivery and request context is destroyed after message delivery
completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
These 2 sentences contradict each other or I am missing some subtleties...
> CDI scopes should be available any message delivery to a MessageListener for a JMS
topic or queue obtained from the Java EE component environment.
>
--------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3107
> URL: https://issues.jboss.org/browse/AS7-3107
> Project: Application Server 7
> Issue Type: Bug
> Components: CDI / Weld, JMS
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
>
> From Martin Kouba:
> I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are
active during message delivery and request context is destroyed after message delivery
completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
> I get following stacktrace (LoggerService is request scoped
bean injected into dependent bean that is registered as javax.jms.MessageListener):
> 15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
> at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
> at org.jboss.weld.Container.instance(Container.java:54)
> at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
> at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
> at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
> at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
> at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
> at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
> at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
> at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
> at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-3107:
----------------------------------
never mind, I found it
https://github.com/jboss/cdi-tck/tree/master/impl/src/main/java/org/jboss...
I'll test it locally
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-3107:
----------------------------------
I have a test in which highlights the issue in
https://github.com/jmesnil/jboss-as/tree/AS7-3107_CDI_MessageListener.
Test is run with ./integration-tests.sh -Dts.noSmoke -Dts.basic
-Dtest=org.jboss.as.test.integration.weld.mdb.MessageListenerInjectionTestCas
Test fails with a different stack trace than previously reported:
{noformat}
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped
at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:619)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104)
at
org.jboss.as.test.integration.weld.mdb.ReverterService$Proxy$_$$_WeldClientProxy.revert(ReverterService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.as.test.integration.weld.mdb.SimpleMessageListener.onMessage(SimpleMessageListener.java:52)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1028)
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1173)
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
{noformat}
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:25 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Martin Kouba commented on AS7-3107:
-----------------------------------
Hi Jeff,
bq. These 2 sentences contradict each other or I am missing some subtleties...
As you evidently realized the problem is in Message-Driven POJOs, not Message-Driven beans
(EJB).
bq. never mind, I found it
https://github.com/jboss/cdi-tck/tree/master/impl/src/main/java/org/jboss...
Yes, this is the valid CDI TCK test.
bq. Test fails with a different stack trace than previously reported
Never mind, the original stack trace is quite old (tested apparently on AS 7.0.x branch).
I get the same stack trace right now (AS 7.1.1).
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:19 a.m.
New subject: [JBoss JIRA] (AS7-3107) CDI scopes should be available any message delivery to a MessageListener for a JMS topic or queue obtained from the Java EE component environment.
[
https://issues.jboss.org/browse/AS7-3107?page=com.atlassian.jira.plugin.s...
]
Martin Kouba closed AS7-3107.
-----------------------------
Resolution: Rejected
This is no longer required by the CDI 1.1 spec (and it was a bug in CDI 1.0).
See CDI-151 for more details.
CDI scopes should be available any message delivery to a
MessageListener for a JMS topic or queue obtained from the Java EE component environment.
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3107
URL: https://issues.jboss.org/browse/AS7-3107
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, JMS
Reporter: Stuart Douglas
Assignee: Stuart Douglas
From Martin Kouba:
I'm just working on CDI TCK tests related to JMS and buil-in contexts - sections
"6.7.1. Request context lifecycle" and "6.7.3. Application context
lifecycle".
I found out that MDBs work great - request and app contexts are active during message
delivery and request context is destroyed after message delivery completes.
However request and app contexts should also be active during "any message delivery
to a MessageListener for a JMS topic or queue obtained from the Java EE component
environment.".
I get following stacktrace (LoggerService is request scoped bean injected into dependent
bean that is registered as javax.jms.MessageListener):
15:10:34,368 WARN [org.hornetq.jms.client.JMSMessageListenerWrapper] (Thread-1
(group:HornetQ-client-global-threads-2012075375)) Unhandled exception thrown from
onMessage: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for
Module "org.hornetq:main" from local module loader @32b0bad7 (roots:
/opt/jboss/jboss-as-weld2/modules)
at
org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73)
at org.jboss.weld.Container.instance(Container.java:54)
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at
org.jboss.jsr299.tck.tests.context.jms.LoggerService$Proxy$_$$_WeldClientProxy.log(LoggerService$Proxy$_$$_WeldClientProxy.java)
at
org.jboss.jsr299.tck.tests.context.jms.AbstractMessageListener.onMessage(AbstractMessageListener.java:19)
at
org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91)
[hornetq-jms-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983)
[hornetq-core-2.2.7.Final.jar:]
at
org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
[hornetq-core-2.2.7.Final.jar:]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Do you know what's happening? Is this feature already implemented in weld/AS7.1
integration?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4516
days inactive
4769
days old
8 comments
4 participants
participants (4)
-
Jeff Mesnil (JIRA) -
Martin Kouba (JIRA)
-
Stuart Douglas (Created) (JIRA)
-
Stuart Douglas (Updated) (JIRA)