[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
I still haven't been able to make much progress on this issue. I've tried various things to see what is going on - from what I can tell while the a transaction is in flight the session is closed in JBoss Messaging, it is as though it doesn't realize that the consumer is active, the session id is that of the consumer that is feeding the MDB. I did discover that some of the comments in my last post aren't quite true - I was looking at a release of the JCA provider that isn't in 5.1.0. It appears that there was a feature added, which added all the traditional stuff into the JCA layer (see https://jira.jboss.org/jira/browse/JBAS-7084). I was wondering if this issue might have any bearing on my problem, since it would imply that maxmessages isn't quite being maintained, and thus maybe this is where my rogue transaction that keeps running and is ultimately cut off in its prime :) Any help or guidance would be greatly appreciated. Cheers P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244553#4244553 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244553 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JCA/JBoss] - stopDelivery on an EJB3 MDB causing an exception when messag
Hi I have been working on a problem that started to appear when we used the stopDelivery method on the MessageContainerWrapper MBean in EJB3. I have posted a couple of forum posts regarding the problem - see: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155887 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155777 I wasn't sure if it was the EJB3 container or the JBM messaging bus that caused the problem and now as I dig deeper it looks like the problem might be in the teardown operation in the JCA connector during endpointdeactivation. In order to show the problem I doctored the EJB3 MDB example code, basically adding in a sleep on the MDB's (to make the transaction hold out so it is running when you call stopDelivery) and also introducing more messages so you have the system under load when you try and stopDelivery. You can grab a copy of these changes here - http://www.fiveclouds.com/stuff/stopdelivery-mdb.zip I didn't want to open a JIRA simply because I'm not sure in which component the problem lies - obviously if you prefer I open one please say and I can get it done. I appreciate any help and thanks in advance P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244714#4244714 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244714 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
After a chat with the very friendly Andy Taylor in the JBoss Messaging room on IRC I have put together a modified version of the EJB3 MDB example, basically you need to run it then while it is consuming messages through JMX execute the stopDelivery (if you don't get an error the first time it is worth trying again). The source is available here - http://www.fiveclouds.com/stuff/stopdelivery-mdb.zip Also I posted to the JCA forum - http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244714#4244714 I'm posting here (not in an attempt to cross post) to allow anyone who stumbles upon this thread to follow it since I'm still not sure if it is a problem in the EJB3 container or JCA. Thanks again for the help - hopefully I'm getting closer to working out what is wrong :) Cheers P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244716#4244716 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244716 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
Thanks for the quick response - I have opened a JIRA https://jira.jboss.org/jira/browse/EJBTHREE-1870 Cheers P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244720#4244720 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244720 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
Its been a while :) but I finally got a little time to dig into this one a
little more, in the end the bit that seems to bite me is the
MessageInflowLocalProxy, when requesting the stopDelivery - messages are
continuing to pass through the MDB. The flow of the requests to stop finally
make it to the MessageInflowProxy which will request a release of the proxy -
due to a small stack of debugging I was sure I had a transaction in flight and
I get to the release method.
|protected void release(Object proxy) throws Throwable
|{
| // We are now released
| released.set(true);
|
| if (trace)
| log.trace("MessageEndpoint " + getProxyString(proxy) + " release "
+ Thread.currentThread());
|
| // Tidyup any outstanding delivery
| if (oldClassLoader != null)
| {
| try
| {
| finish("release", proxy, false);
| }
| catch (Throwable t)
| {
| log.warn("Error in release ", t);
| }
| }
|}
|
What I don't understand is that the oldClassLoader is null which means that the
finish didn't get called - looking at that method that means that the finish
doesn't get called and the transaction manager didn't get tidied up.
So I continued to dig around to see where the oldClassLoader gets set - it
looks like it is done in the before and after, which would imply that the
TransactionDemarcationStrategy in the JmsServerSession needs to be
TraditionalXATransactionDemarcationStrategy (since that it checked for) in the
onMessage. I appear to have an XATransactionDemarcationStrategy in place so
before and after aren't called.
It looked like in the MessageInflowLocalProxy you look for the oldClassLoader
in the delivery method too - if it is null you start a transaction.
| try
| {
| // Check for starting a transaction
| if (oldClassLoader == null)
| {
| boolean isTransacted =
messageEndpointFactory.isDeliveryTransacted(methodInfo.getAdvisedMethod());
| startTransaction("delivery", proxy, container, method, args,
isTransacted);
| }
| return container.localInvoke(methodInfo, args);
| }
|
when you try to release how do you perform the check to ensure that the
transaction has completed (when the oldClassLoader is null)?
All this code is pretty new to me so excuse any things that I got patently
wrong :) Any advice or help would be greatly appreciated.
Cheers
P
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243625#4243625
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243625
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
We are still looking into this - I had a quick question around the way in which a JBMActivation stops, it looks like you stop delivery and then start a teardown. As I'm following it when I choose stopDelivery on the MDB it then requested deactiveEndpoint in the reosource adapter which finally gets to call stop on the JBMActivation which sets deliveryActive to false then calls teardown on the JBMMessageHandler which releases the endpoint and closes the session. If the message is currently being consumed shouldn't this be waiting for that transaction? I'm wondering if this is causing the session can not be found when the in-flight transaction completes? All help is greatly appreciated :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236832#4236832 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236832 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
I posted back to the JBM forum (I'm sorry I keep jumping between them) http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155777&start=10&postdays=postDays&postorder=postOrder&highlight=highlight The MDB in question is an EJB3 deployed one and it is the EJB3 container, the MBean is listed as org.jboss.ejb3.mdb.MessagingDelegateWrapper. We are calling the stopDelivery method on this to try and pause message consumption and that is when we get the exception. I have checked the MDB and there is no funky threading stuff going on it there. Since stopDelivery is new I'm wondering if there is a threading problem in the container, though this occurs where we have MaxMessages and JMS Sessions both a 1 (and it also occurs where JMS sessions is set to a higher value). Once again thanks for all the help P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234528#4234528 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234528 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
Thanks for all the help and insight - I'll jump back over to EJB3 and see if maybe it is a configuration issue in the deployment or a problem in the EJB3 container (since stopDelivery was only recently added). Thanks again P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234527#4234527 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234527 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
We have continued to work on this one - and have upgraded to the latest JBoss 5.1.0GA release. This appears to have resolved the problem with the XA transaction - however we are using the stopDelivery method on the EJB3 MDB MBean and are getting a "session cannot be found" during the stopDelivery processing. I'm not certain if it is a problem in the MDB container or the JBoss Messaging configuration, I have opened a discussion over on the EJB3 forum, see: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155887 I really didn't want to cross post stuff but I was wondering if any JBM guys could spot something in the trace, it looks like it rolls back ok - and we are trying to work out whether this is a problem that we need to look into or just the way things are when you stop delivery. Thanks again for all the help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234511#4234511 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234511 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes a
We are calling the stopDelivery method on the EJB3 MDB MBean - I believe this one is the container registered when deploying the MDB. The stopDelivery functionality was only re-introduced recently (I believe maybe 1.1.2/1.1.3?) and we have been keen to make use of it. Thanks for the reply and the continuing help :) Cheers P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234506#4234506 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234506 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Calling stopDelivery causes an exception
We have upgraded to JBoss 5.1.0GA and the problem is the same, is it a known issue, or an exception we can safely ignore? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234361#4234361 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234361 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Calling stopDelivery causes a
I am currently running a JBoss 5.0.1GA with an updated EJB3 container (1.1.4). I upgraded the container so that I could use the stopDelivery/startDelivery functionality on the MDB's. When we call stopDelivery and startDelivery through JMX they do seem to function as expected, however on the stopDelivery we get | 15:28:07,069 ERROR [ExceptionUtil] ConnectionEndpoint[s73-tbaaa1vf-1-j8ot91vf-maz9g4-b1r27p4] sendTransaction [hc3-17yaa1vf-1-j8ot91vf-maz9g4-b1r27p4] | javax.jms.IllegalStateException: Cannot find session with id v73-vbaaa1vf-1-j8ot91vf-maz9g4-b1r27p4 | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489) | 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_N326865078927536.invokeTarget(ConnectionAdvised$sendTransaction_N326865078927536.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.GeneratedMethodAccessor502.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_N326865078927536.invokeTarget(ClientConnectionDelegate$sendTransaction_N326865078927536.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.commit(ResourceManager.java:367) | at org.jboss.jms.tx.MessagingXAResource.commit(MessagingXAResource.java:254) | at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:800) | at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2639) | at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1784) | 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 co
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
This is just a single JBoss instance, and the only one on the network while we are testing. The persistence if using Oracle 11g to a database on a second server. Thanks again P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232505#4232505 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232505 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
We are running on a JBoss 5.0.1GA base, though we needed the startDelivery and stopDelivery methods to exist on the MDB container therefore we upgraded the EJB 3.0 container to 1.1.4(?). Judging from the log its a JBoss 1.4.1.GA server, this is just what came with the server. | 2009-05-20 12:29:01,038 INFO [org.jboss.jms.server.ServerPeer] (main) JBoss Messaging 1.4.1.GA server [0] started | The shutdown we are seeing just being initiated by a control+C on the terminal. If we don't have messages processing the shutdown is clean. Thanks again P View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232489#4232489 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232489 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Cannot find session during shutdown
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_N326865078927536.invokeTarget(ConnectionAdvised$sendTransaction_N326865078927536.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_N326865078927536.invokeTarget(ClientConnectionDelegate$sendTransaction_N326865078927536.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) |
[jboss-user] [JBoss Messaging] - Cannot find session during shutdown
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_N326865078927536.invokeTarget(ConnectionAdvised$sendTransaction_N326865078927536.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, 49454551102535510210157555899565550585297495250102995758575345511025355102101575558995655505852974952501029957585754 > 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 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
