[JBoss Messaging] - Re: Cannot find session during shutdown
by philipdodds
Hi Clebert
We have put in the recovery settings into the jbossjta-properties.xml and also moved it to the top during testing.
It worries me a little that the session isn't found - I could only find references to that problem occurring in a clustered environment (see https://jira.jboss.org/jira/browse/JBESB-2218) though we are seeing this:
| 2009-05-20 12:30:52,499 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkManager(2)-44) ConnectionEndpoint[fe-oz919yuf-1-mj809yuf-bruz48-x21o4c5] sendTransaction [ur4-b6b39yuf-1-mj809yuf-bruz48-x21o4c5]
| javax.jms.IllegalStateException: Cannot find session with id ie-qz919yuf-1-mj809yuf-bruz48-x21o4c5
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:497)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeTarget(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195)
| at sun.reflect.GeneratedMethodAccessor345.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java)
| at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
| at org.jboss.remoting.Client.invoke(Client.java:1708)
| at org.jboss.remoting.Client.invoke(Client.java:612)
| at org.jboss.remoting.Client.invoke(Client.java:600)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N3268650789275322226.invokeTarget(ClientConnectionDelegate$sendTransaction_N3268650789275322226.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.sendTransaction(ClientConnectionDelegate.java)
| at org.jboss.jms.tx.ResourceManager.sendTransactionXA(ResourceManager.java:662)
| at org.jboss.jms.tx.ResourceManager.prepare(ResourceManager.java:337)
| at org.jboss.jms.tx.MessagingXAResource.prepare(MessagingXAResource.java:240)
| at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:271)
| at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2893)
| at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2850)
| at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2402)
| at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1790)
| at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88)
| at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1414)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
| at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:657)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:243)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:613)
| 2009-05-20 12:30:52,502 WARN [com.arjuna.ats.jta.logging.loggerI18N] (WorkManager(2)-44) [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception XAException.XA_RETRY
| 2009-05-20 12:30:52,503 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkManager(2)-44) [com.arjuna.ats.arjuna.coordinator.BasicAction_50] - Prepare phase of action -3f57fe97:c872:4a142fc9:7795 received heuristic decision: TwoPhaseOutcome.HEURISTIC_HAZARD
| 2009-05-20 12:30:52,503 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkManager(2)-44) [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id -3f57fe97:c872:4a142fc9:7795 failed.
| 2009-05-20 12:30:52,503 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkManager(2)-44) [com.arjuna.ats.arjuna.coordinator.BasicAction_37] - Received heuristic: TwoPhaseOutcome.HEURISTIC_HAZARD .
| 2009-05-20 12:30:52,503 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (WorkManager(2)-44) [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting
| 2009-05-20 12:30:52,504 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (WorkManager(2)-44) org.jboss.resource.adapter.jms.inflow.JmsServerSession@8e4361 failed to commit/rollback
| javax.transaction.HeuristicMixedException
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1422)
| at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
| at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:657)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:243)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
| at java.lang.Thread.run(Thread.java:613)
|
The HeuristicMixedException worries me - and noticed that this ticket - https://cloud.prod.atl2.jboss.com:8443/jira/browse/JBESB-2483 seemed to indicate a possible problem in JBM? I wondered if you have seen it or had any advice on what to look at? I'm not saying there might not be a problem in the code - it is an MDB that communicates to an Oracle database and XA is in place across all sides of the transaction - also JBM is running on the same Oracle database (if that helps)
Thanks again for the quick response
P
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232357#4232357
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232357
16 years, 11 months
[Management, JMX/JBoss] - MBean POJO(jboss ejb3 annotations) NOT working in jboss 5
by yashendrac
I am not able to deploy MBean POJO in jboss 5 though it works in jboss4.
I have an MBean POJO developed using jboss ejb3 annotations @Service and @Management
something like this :
import org.jboss.ejb3.annotation.Management;
| import org.jboss.ejb3.annotation.Service;
| import javax.ejb.EJB;
| @Management( KeyStoreServiceMBean.class )
| @Service( objectName = "smc.jboss:service=KeyStoreService" )
| public class KeyStoreService implements KeyStoreServiceMBean {
|
| @EJB
| private KeyStoreSession keyStoreSessionBean;
| ...
| ...
| }
|
As using jboss ejb3 annotation, in place of bundling in .sar with *-service or *-bean. I have directly bundled it in jar and there is no *-service or *-bean xml for defining this MBean.
This same jar gets deployed without any complaint in jboss 4 but it never gets deployed in jboss 5 only message i see in log is
2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:ear=core.ear,jar=core.jar,name=KeyStoreService,service=EJB3) to KernelDeployment of: core.jar
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:ear=core.ear,jar=core.jar,name=AlarmsListener,service=EJB3
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies:
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands:
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232351#4232351
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232351
16 years, 11 months
[Management, JMX/JBoss] - Re: JBoss 5: MBean depends on EJB3 Staleless Bean according
by yashendrac
I am also getting some problem with MBean in jboss 5.
I have an MBean POJO developed using jboss ejb3 annotations @Service and @Management
something like this :
import org.jboss.ejb3.annotation.Management;
| import org.jboss.ejb3.annotation.Service;
| import javax.ejb.EJB;
| @Management( KeyStoreServiceMBean.class )
| @Service( objectName = "smc.jboss:service=KeyStoreService" )
| public class KeyStoreService implements KeyStoreServiceMBean {
|
| @EJB
| private KeyStoreSession keyStoreSessionBean;
| ...
| ...
| }
|
As using jboss ejb3 annotation, in place of bundling in .sar with *-service or *-bean. I have directly bundled it in jar and there is no *-service or *-bean xml for defining this MBean.
This same jar gets deployed without any complaint in jboss 4 but it never gets deployed in jboss 5 only message i see in log is
2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] Added bean(jboss.j2ee:ear=core.ear,jar=core.jar,name=KeyStoreService,service=EJB3) to KernelDeployment of: core.jar
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] installing bean: jboss.j2ee:ear=core.ear,jar=core.jar,name=AlarmsListener,service=EJB3
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] with dependencies:
| 2009-05-20 16:25:42,877 INFO [org.jboss.ejb3.deployers.JBossASKernel] and demands:
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232349#4232349
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232349
16 years, 11 months
[JBoss Messaging] - Cannot find session during shutdown
by philipdodds
During the shutdown of a system with several MDB's we appear to be getting:
| 2009-05-20 12:30:52,499 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkManager(2)-44) ConnectionEndpoint[fe-oz919yuf-1-mj809yuf-bruz48-x21o4c5] sendTransaction [ur4-b6b39yuf-1-mj809yuf-bruz48-x21o4c5]
| javax.jms.IllegalStateException: Cannot find session with id ie-qz919yuf-1-mj809yuf-bruz48-x21o4c5
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:497)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeTarget(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
|
This seems to lead to
2009-05-20 12:36:34,251 WARN [com.arjuna.ats.jta.logging.loggerI18N] (Thread-13) [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 4945455110253551021015755589956555058529749525010299575855555753455110253551021015755589956555058529749525010299575855555754 >
When the server restarts, what causes problems with the session not being found in a XA environment?
Thanks in advance
Philip
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232348#4232348
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232348
16 years, 11 months