[JBoss JIRA] Created: (JBAS-7579) UnifiedInvokerHAProxy does not always record that invocation has reached a server
by Brian Stansberry (JIRA)
UnifiedInvokerHAProxy does not always record that invocation has reached a server
---------------------------------------------------------------------------------
Key: JBAS-7579
URL: https://jira.jboss.org/jira/browse/JBAS-7579
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-6.0.0.M1
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-6.0.0.M2
This class uses the invocationHasReachedAServer() method to ensure transactions stickiness is maintained. In some cases the method isn't called, generally in catch blocks where the caught exception is rethrown. The method should be called even though the exception is going to be thrown, because the client application may catch and handle the exception and not abort any ongoing transaction.
--
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, 5 months
[JBoss JIRA] Created: (JBRULES-2236) Is MVEL upgrade for Drools 4.0.7 available?
by Jayanth Seshadri (JIRA)
Is MVEL upgrade for Drools 4.0.7 available?
-------------------------------------------
Key: JBRULES-2236
URL: https://jira.jboss.org/jira/browse/JBRULES-2236
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.7
Environment: UNIX
Reporter: Jayanth Seshadri
Assignee: Mark Proctor
We are using Drools 4.0.7 which ships with the mvel-1.3.1-java1.4.jar dependency. At times, we get the following MVEL error (stack trace below) and the Rule Engine skips processing some records. However, during a second run with the same data set we do not get the same error.
What we would like to know is if there is a way to upgrade the MVEL jar in Drools 4.0.7?
Please see stack trace below:
at org.mvel.MVELRuntime.execute(MVELRuntime.java:90)
at org.mvel.CompiledExpression.getValue(CompiledExpression.java:111)
at org.mvel.MVEL.executeExpression(MVEL.java:235)
at org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:45)
at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:209)
... 16 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.loadClass(ASMAccessorOptimizer.java:1003)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer._initializeAccessor(ASMAccessorOptimizer.java:206)
at org.mvel.optimizers.impl.asm.ASMAccessorOptimizer.compileAccessor(ASMAccessorOptimizer.java:264)
... 31 more
Caused by: java.lang.LinkageError: ASMAccessorImpl_1246513741246377473850
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:223)
at java.lang.ClassLoader.defineClass(ClassLoader.java:162)
... 37 more
Jun 30, 2009 10:57:53 AM walgreens.pbs.ruleengine.worker.RulesetExecutor run
WARNING: Exception caught while processing data from row 150001 to 155000
--
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, 5 months
[JBoss JIRA] Closed: (JBAS-8302) Message Driven Beans fail to run if an item is on the queue before the application server is started up
by Marius Bogoevici (JIRA)
[ https://jira.jboss.org/browse/JBAS-8302?page=com.atlassian.jira.plugin.sy... ]
Marius Bogoevici closed JBAS-8302.
----------------------------------
Resolution: Done
Closing, as the BeanManager is initialized now correctly, before EJBs start.
> 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.Final
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Commented: (JBAS-8302) Message Driven Beans fail to run if an item is on the queue before the application server is started up
by Adolfo Luna (JIRA)
[ https://jira.jboss.org/browse/JBAS-8302?page=com.atlassian.jira.plugin.sy... ]
Adolfo Luna commented on JBAS-8302:
-----------------------------------
I downloaded and compiled "trunk" version, but i wasn't able to reproduce the error.
As soon as the MDB is started, the pending message is readed.
> 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.Final
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBAS-8637) twiddle does not correctly handle IPv6 addresses
by Richard Achmatowicz (JIRA)
twiddle does not correctly handle IPv6 addresses
------------------------------------------------
Key: JBAS-8637
URL: https://jira.jboss.org/browse/JBAS-8637
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Integration
Affects Versions: 6.0.0.M4
Reporter: Richard Achmatowicz
Assignee: Scott Marlow
Fix For: TBD-6.x
When starting the AS with an IPv6 bind address, the following WARN log entry is seen on the console:
17:04:10,765 INFO [SnmpAgentService] SNMP agent going active
17:04:10,783 ERROR [TrapEmitter] SNMP send error for localhost/127.0.0.1:1162: <java.security.InvalidParameterException: Buffer overflow error converting IP address>
17:04:11,030 WARN [InvokerLocator] Host resolves to null in socket://3ffe:ffff:100:f101::1:3873?timeout=300000. Perhaps the host contains an invalid character. See http://www.ietf.org/rfc/rfc2396.txt.
17:04:11,465 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
THis is due to the InvokerLocator for the MBean
jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
being incorrectlly formed by substitution of the bind address into the URL template in the file deploy/ejb3-connection-jboss-beans.xml
socket://${jboss.bind.address}:${port}?timeout=300000
In order to create a well-formed URL, this needs to check for the case when the bind address is an IPv6 literal, and add brackets accordingly.
--
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, 5 months
[JBoss JIRA] Created: (JBAS-8453) InvokerLocator for default EJB Connector being formed incorrectly with IPv6 bind address
by Richard Achmatowicz (JIRA)
InvokerLocator for default EJB Connector being formed incorrectly with IPv6 bind address
----------------------------------------------------------------------------------------
Key: JBAS-8453
URL: https://jira.jboss.org/browse/JBAS-8453
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Integration
Affects Versions: 6.0.0.M4
Reporter: Richard Achmatowicz
Assignee: Scott Stark
Fix For: TBD-6.x
When starting the AS with an IPv6 bind address, the following WARN log entry is seen on the console:
17:04:10,765 INFO [SnmpAgentService] SNMP agent going active
17:04:10,783 ERROR [TrapEmitter] SNMP send error for localhost/127.0.0.1:1162: <java.security.InvalidParameterException: Buffer overflow error converting IP address>
17:04:11,030 WARN [InvokerLocator] Host resolves to null in socket://3ffe:ffff:100:f101::1:3873?timeout=300000. Perhaps the host contains an invalid character. See http://www.ietf.org/rfc/rfc2396.txt.
17:04:11,465 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
THis is due to the InvokerLocator for the MBean
jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
being incorrectlly formed by substitution of the bind address into the URL template in the file deploy/ejb3-connection-jboss-beans.xml
socket://${jboss.bind.address}:${port}?timeout=300000
In order to create a well-formed URL, this needs to check for the case when the bind address is an IPv6 literal, and add brackets accordingly.
--
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, 5 months
[JBoss JIRA] Created: (JBMETA-317) JBossMetaData.getInterceptors(String beanName, JBossMetaData jbossMetaData) doesn't take into account interceptor-order
by jaikiran pai (JIRA)
JBossMetaData.getInterceptors(String beanName, JBossMetaData jbossMetaData) doesn't take into account interceptor-order
-----------------------------------------------------------------------------------------------------------------------
Key: JBMETA-317
URL: https://jira.jboss.org/browse/JBMETA-317
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ejb
Affects Versions: jboss-metadata-ejb-2.0.0-alpha-24
Reporter: jaikiran pai
Assignee: jaikiran pai
Consider the following ejb-jar.xml:
<assembly-descriptor>
<interceptor-binding>
<ejb-name>mybean</ejb-name>
<interceptor-order>
<interceptor-class>org.myapp.MyInterceptor</interceptor-class>
</interceptor-order>
</interceptor-binding>
</assembly-descriptor>
Currently, JBossMetaData.getInterceptors doesn't check the interceptor-order on the binding and instead just checks for interceptor-classes. This results in the method return empty interceptors for the bean.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months