[JBoss JIRA] Created: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
6:15 p.m.
EJBTransactionRolledBackException in EJB3 application after bringing down the first member
of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Brian Stansberry
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 p.m.
New subject: [JBoss JIRA] Commented: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=comments#action_1234... ]
Phillip Thurmond commented on JBCLUSTER-155:
--------------------------------------------
javax.ejb.EJBTransactionRolledbackException:
java.lang.reflect.UndeclaredThrowableException at
org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93) at
org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at
org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.remoting.ReplicantsManagerInterceptor.invoke(ReplicantsManagerInterceptor.java:51)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at
org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:211) at
org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79) at
$Proxy101.allocateInventory(Unknown Source) at
services.ejb.OrderEntryProcessCoordinatorBean.processOrder(OrderEntryProcessCoordinatorBean.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:585) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at
org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
at
org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at
org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.remoting.ReplicantsManagerInterceptor.invoke(ReplicantsManagerInterceptor.java:51)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at
org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:211) at
org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79) at
$Proxy123.processOrder(Unknown Source) at
services.web.NewOrderServlet.doPost(NewOrderServlet.java:130) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at
org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:87)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595) Caused by:
java.lang.reflect.UndeclaredThrowableException at $Proxy131.replenishInventory(Unknown
Source) at
services.ejb.InventoryManagerBean.replenishInventory(InventoryManagerBean.java:95) at
services.ejb.InventoryManagerBean.allocateInventory(InventoryManagerBean.java:80) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:585) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at
org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
at
org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 73 more Caused by:
javax.jms.IllegalStateException: The session is closed at
org.jboss.mq.SpySession.checkClosed(SpySession.java:1149) at
org.jboss.mq.SpySession.createObjectMessage(SpySession.java:280) at
org.jboss.ejb3.mdb.ProducerManagerImpl.invoke(ProducerManagerImpl.java:262) at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at
org.jboss.ejb3.mdb.ProducerProxy.invoke(ProducerProxy.java:63) ... 89 more
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Brian Stansberry
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:29 a.m.
New subject: [JBoss JIRA] Commented: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=comments#action_1234... ]
Brian Stansberry commented on JBCLUSTER-155:
--------------------------------------------
From looking at this stack trace and the code, it looks like some
issue in the ProducerProxy and ProducerManagerImpl where an attempt is being made to use a
closed session. Probably the session is closed because the JMS server failed over when you
shut down the first instance. Somewhere in the code there needs to be a check for a failed
JMS connection (which happens for sure when the JMS server fails over) and a reconnect. I
don't know enough about this code to know where that should be -- in the test beans in
this ProducerProxy/ProducerManager stuff.
I'll attach a simple JMS client class that illustrates how to detect a failover and
reconnect. Again, I don't know where in your code this should be implemented. The
implementation of reconnecting will almost for sure be different from the attached class;
the attached class is more to demonstrate how to be aware of a failure.
If you think this reconnect should be done in the org.jboss.ejb3 code, please open a forum
thread to discuss, and if necessary, a JIRA issue in the EJB3 project.
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Brian Stansberry
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:32 a.m.
New subject: [JBoss JIRA] Updated: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=all ]
Brian Stansberry updated JBCLUSTER-155:
---------------------------------------
Attachment: FailoverJMSClient.java
Attached an example of a client that handles HA-JMS failover.
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Brian Stansberry
Attachments: FailoverJMSClient.java
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Assigned: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=all ]
Brian Stansberry reassigned JBCLUSTER-155:
------------------------------------------
Assignee: Phillip Thurmond (was: Brian Stansberry)
Philip, could you close this JIRA out, with a link to any other issue that was opened to
track the fix?
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Attachments: FailoverJMSClient.java
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 p.m.
New subject: [JBoss JIRA] Commented: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=comments#action_1235... ]
Brian Stansberry commented on JBCLUSTER-155:
--------------------------------------------
Please resolve it as a Duplicate with no Fix Version.
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Attachments: FailoverJMSClient.java
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 p.m.
New subject: [JBoss JIRA] Resolved: (JBCLUSTER-155) EJBTransactionRolledBackException in EJB3 application after bringing down the first member of the cluster.
[ http://jira.jboss.com/jira/browse/JBCLUSTER-155?page=all ]
Phillip Thurmond resolved JBCLUSTER-155.
----------------------------------------
Resolution: Done
EJBTransactionRolledBackException in EJB3 application after bringing
down the first member of the cluster.
----------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-155
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-155
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: Q4Y6
Environment: Clustering QA Lab. Linux x86_64 on Sun jdk 1.5
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Attachments: FailoverJMSClient.java
Using the ejb3 application at https://svn.jboss.org/repos/qa/ejb3demo . JBoss 4.0.5.GA
with ejb3 from https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_EJBTHREE-798/ .
I create two identical server configurations for the ejb3demo application from the all
config. I enable query caching in persistence.xml. To reproduce:
1. start up first instance, place order.
2. start up second instance, watch for cluster notification and join. Place order on
second and first instances.
3. bring down first instance, watch for cluster removal messages on second host. Place
order and receive an EJBTransactionRolledBackException in the browser. No stack traces or
error messages are logged on the console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7007
days inactive
7113
days old
6 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Brian Stansberry (JIRA) -
Phillip Thurmond (JIRA)
-
Phillip Thurmond (JIRA)