August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7377) Add JSR-330 Dependency Injection APIs needed for WELD

by Shelly McGowan (JIRA)

Add JSR-330 Dependency Injection APIs needed for WELD ----------------------------------------------------- Key: JBAS-7377 URL: https://jira.jboss.org/jira/browse/JBAS-7377 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Beans Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: JBossAS-5.2.0.Beta1 Include javax.inject APIs in AS 5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7792) WeldJndiBinder incompatible with new EE6 namespace code

by Jason T. Greene (JIRA)

WeldJndiBinder incompatible with new EE6 namespace code ------------------------------------------------------- Key: JBAS-7792 URL: https://jira.jboss.org/jira/browse/JBAS-7792 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assignee: Marius Bogoevici Priority: Blocker 11:36:57,316 WARN [StartStopLifecycleAction] Error during stopService for WeldJndiBinder: javax.naming.NameNotFoundException: app not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.unbind(NamingServer.java:315) at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:873) at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:856) at javax.naming.InitialContext.unbind(InitialContext.java:416) at org.jboss.weld.integration.deployer.env.WeldJndiBinder.stopService(WeldJndiBinder.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Moved: (JBAS-8305) TransactionSynchronizationRegistry should be looked up from "java:comp/TransactionSynchronizationRegistry"

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8305?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-41 to JBAS-8305: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8305 (was: WELDINT-41) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > TransactionSynchronizationRegistry should be looked up from "java:comp/TransactionSynchronizationRegistry" > ---------------------------------------------------------------------------------------------------------- > > Key: JBAS-8305 > URL: https://jira.jboss.org/browse/JBAS-8305 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Koichi Kobayashi > Fix For: 6.0.0.CR1 > > > See EE.5.11 in JavaEE6 spec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8304) Use shared library mode in JBoss AS

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8304?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-4 to JBAS-8304: --------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8304 (was: WELDINT-4) Component/s: Weld/CDI (was: Weld Bootstrapper) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Use shared library mode in JBoss AS > ----------------------------------- > > Key: JBAS-8304 > URL: https://jira.jboss.org/browse/JBAS-8304 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 6.0.0.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8298) WeldBootstrap class is leaked through application CL

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8298?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-51 to JBAS-8298: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8298 (was: WELDINT-51) Component/s: Weld/CDI (was: Weld Bootstrapper) > WeldBootstrap class is leaked through application CL > ---------------------------------------------------- > > Key: JBAS-8298 > URL: https://jira.jboss.org/browse/JBAS-8298 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: David Allen > > The WeldBootstrap class is being added as a dependency in the JBoss AS dependency controller. Since this class is loaded within a deployment's classloader, every deployment CL is leaked. > I will be working on identifying where this dependency is generated and try to identify a fix for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8299) NPE in Weld when a portable extension is added by JBoss AS deployer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8299?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-58 to JBAS-8299: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8299 (was: WELDINT-58) > NPE in Weld when a portable extension is added by JBoss AS deployer > ------------------------------------------------------------------- > > Key: JBAS-8299 > URL: https://jira.jboss.org/browse/JBAS-8299 > Project: JBoss Application Server > Issue Type: Bug > Environment: JBoss AS 6 M2 > JDK 6 > Reporter: Jozef Hartinger > Attachments: jboss-as-resteasy-6.0.0-SNAPSHOT-sources.jar, resteasy-cdi-sources.jar, resteasy-cdi.war, resteasy-int-all.zip, stacktrace.txt > > > I am getting a NPE in Weld when I try to add a portable extension to an application using PathUrlIntegrationDeployer. (See stacktrace.txt for details) Note that everything works OK when the portable extension is bundled physically with the application. > To reproduce: > 1) Take a fresh JBoss AS 6 M2 > 2) Remove RESTEasy deployer (rm -r ${JBOSS_HOME}/server/default/deployers/resteasy-deployer) > 3) Replace the old RESTEasy deployer with a new one (unzip resteasy-int-all.zip -d ${JBOSS_HOME}/server/default/deployers) > 4) Start the AS in default configuration > 5) Deploy the testing application (cp resteasy-cdi.war ${JBOSS_HOME}/server/default/deploy) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8300) web.xml configured jsf error-page throws ContextNotActiveException

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8300?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-43 to JBAS-8300: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8300 (was: WELDINT-43) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > web.xml configured jsf error-page throws ContextNotActiveException > ------------------------------------------------------------------ > > Key: JBAS-8300 > URL: https://jira.jboss.org/browse/JBAS-8300 > Project: JBoss Application Server > Issue Type: Bug > Environment: glassfish V3 prelude, jsf 2.0.0-SNAPSHOT (May 17 2009) > Reporter: Guy Veraghtert > Assignee: Pete Muir > Fix For: 6.0.0.CR1 > > > An ContextNotActiveException is thrown by Web beans when the container tries to forward to a jsf error-page (configured in web.xml). See forum reference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8301) WeldListener should be the first Servlet Listener to fire

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8301?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-56 to JBAS-8301: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8301 (was: WELDINT-56) Component/s: Weld/CDI (was: JBoss Services (Other)) > WeldListener should be the first Servlet Listener to fire > --------------------------------------------------------- > > Key: JBAS-8301 > URL: https://jira.jboss.org/browse/JBAS-8301 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Nicklas Karlsson > Priority: Critical > > The WeldListener should be the first ServletListener to fire since if it's not, the CDI contexts etc. are not available for any application ServletListener that might want to use these features -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8303) Investigate better ways of doing injection into into EJB instances than using an interceptor

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8303?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-9 to JBAS-8303: --------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8303 (was: WELDINT-9) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Investigate better ways of doing injection into into EJB instances than using an interceptor > -------------------------------------------------------------------------------------------- > > Key: JBAS-8303 > URL: https://jira.jboss.org/browse/JBAS-8303 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Fix For: 6.0.0.CR1 > > > Especially, a better way of getting the EJB name -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8302) Message Driven Beans fail to run if an item is on the queue before the application server is started up

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8302?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-61 to JBAS-8302: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8302 (was: WELDINT-61) Component/s: Weld/CDI (was: Weld Bootstrapper) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Message Driven Beans fail to run if an item is on the queue before the application server is started up > ------------------------------------------------------------------------------------------------------- > > Key: JBAS-8302 > URL: https://jira.jboss.org/browse/JBAS-8302 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0-M3 with Weld 1.0.1-Final > Reporter: Ian > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > The scenario occurs when I start up an application with an MDB and there is a message on the queue before the application starts. If a message appears on the queue after application startup, there are no issues and everything processes correctly. During application startup, I get "StackTrace #1" - the error is to do with being unable to locate the BeanManager. After the application starts up, I continually get "StackTrace #2" - which means no further messages ever get delivered to the MDB. > StackTrace #1 > 11:08:53,949 ERROR [org.jboss.aspects.tx.TxPolicy] javax.ejb.EJBTransactionRolledbackException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > 11:08:53,949 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] Failed to deliver message: javax.ejb.EJBTransactionRolledbackException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115) [:1.0.2] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) [:1.0.0.GA] > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194) [:1.0.0.GA] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.2] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:277) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) [:1.3.1] > at $Proxy171.onMessage(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:259) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:809) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:927) [:6.0.0.20100429-M3] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:96) [:6.0.0.20100429-M3] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11] > at java.lang.Thread.run(Thread.java:619) [:1.6.0_11] > Caused by: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:82) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:99) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:89) [:1.3.1] > at org.jboss.ejb3.interceptor.InterceptorInjector.inject(InterceptorInjector.java:49) [:1.3.1] > at org.jboss.ejb3.EJBContainer.createInterceptor(EJBContainer.java:359) [:1.3.1] > at org.jboss.ejb3.BaseContext.initialiseInterceptorInstances(BaseContext.java:112) [:1.3.1] > at org.jboss.ejb3.injection.InjectionHelper.inject(InjectionHelper.java:55) [:1.3.1] > at org.jboss.ejb3.injection.InjectionHelper.inject(InjectionHelper.java:43) [:1.3.1] > at org.jboss.ejb3.mdb.MDBInjectionInvocation.proceed(MDBInjectionInvocation.java:45) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:97) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:91) [:1.3.1] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:82) [:1.3.1] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:82) [:1.3.1] > at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1197) [:1.3.1] > at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:83) [:1.3.1] > at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:73) [:1.3.1] > at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:146) [:1.3.1] > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) [:1.0.0.GA] > ... 26 more > Caused by: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NamingException: WELD-001300 Unable to locate BeanManager] > at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1356) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:819) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_11] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_11] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_11] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_11] > at org.jboss.ejb3.EJBContainer$1.invoke(EJBContainer.java:828) [:1.3.1] > at $Proxy163.lookup(Unknown Source) at org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:75) [:1.3.1] > ... 47 more > Caused by: javax.naming.NamingException: WELD-001300 Unable to locate BeanManager > at org.jboss.weld.resources.ManagerObjectFactory.getObjectInstance(ManagerObjectFactory.java:50) [:1.0.1.Final] > at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) [:1.6.0_11] > at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:824) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final] > at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_11] > at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1350) [:5.0.5.Final] > ... 57 more > StackTrace #2 > 11:09:14,777 ERROR [org.jboss.aspects.tx.TxPolicy] javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 > 11:09:14,777 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] Failed to deliver message: javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 > at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:127) [:1.3.1] > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) [:1.0.0.GA] > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194) [:1.0.0.GA] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.2] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:277) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) [:1.3.1] > at $Proxy171.onMessage(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:259) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:809) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:927) [:6.0.0.20100429-M3] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:96) [:6.0.0.20100429-M3] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11] > at java.lang.Thread.run(Thread.java:619) [:1.6.0_11] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2010