2 Replies Latest reply on Mar 22, 2002 11:38 AM by jeffdelong

    TRANSACTION ROLLBACK EXCEPTION

    houdum

      I've got some troubles with JBoss2.4.4 and Catalina

      Can you help me ?

      This my log message :
      [09:52:22,526,Default] JBoss-2.4.4 Started in 0m:10s.609
      [09:52:48,870,LRUEnterpriseContextCachePolicy] Resized cache for bean group: old capacity = 1000, new capacity = 50
      [09:52:49,214,sessionLog] TRANSACTION ROLLBACK EXCEPTION:
      javax.transaction.TransactionRolledbackException: Application Error: tried to enter Stateful bean with different transaction context; nested exception is:
      java.rmi.RemoteException: Application Error: tried to enter Stateful bean with different transaction context
      java.rmi.RemoteException: Application Error: tried to enter Stateful bean with different transaction context
      at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:206)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:138)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:347)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:100)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:170)
      at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:339)
      at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:410)
      at java.lang.reflect.Method.invoke(Native Method)
      at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
      at sun.rmi.transport.Transport$1.run(Transport.java:152)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.rmi.transport.Transport.serviceCall(Transport.java:148)
      at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706)
      at java.lang.Thread.run(Thread.java:484)
      [09:52:54,073,LRUEnterpriseContextCachePolicy] Resized cache for bean domainsApplications: old capacity = 1000, new capacity = 50
      [09:53:57,198,LRUEnterpriseContextCachePolicy] Resized cache for bean domain: old capacity = 1000, new capacity = 50
      [09:53:59,714,LRUEnterpriseContextCachePolicy] Resized cache for bean sessionLog: old capacity = 1000, new capacity = 50
      [09:55:17,042,LRUEnterpriseContextCachePolicy] Resized cache for bean application: old capacity = 1000, new capacity = 50
      [09:55:31,104,LRUEnterpriseContextCachePolicy] Resized cache for bean user: old capacity = 1000, new capacity = 50
      [09:55:43,761,LRUEnterpriseContextCachePolicy] Resized cache for bean groupsApplications: old capacity = 1000, new capacity = 50
      [09:59:48,792,sessionLog] TRANSACTION ROLLBACK EXCEPTION:
      javax.transaction.TransactionRolledbackException: Application Error: tried to enter Stateful bean with different transaction context; nested exception is:
      java.rmi.RemoteException: Application Error: tried to enter Stateful bean with different transaction context
      java.rmi.RemoteException: Application Error: tried to enter Stateful bean with different transaction context
      at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:206)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:138)
      at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:347)
      at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:100)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:170)
      at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:339)
      at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:410)
      at java.lang.reflect.Method.invoke(Native Method)
      at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
      at sun.rmi.transport.Transport$1.run(Transport.java:152)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.rmi.transport.Transport.serviceCall(Transport.java:148)
      at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706)
      at java.lang.Thread.run(Thread.java:484)
      [10:09:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@18b8b64c - Cache size = 9
      [10:09:52,479,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@4826b017 - Cache size = 8
      [10:09:52,479,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@7ef86365 - Cache size = 7
      [10:09:52,479,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@7eabc196 - Cache size = 6
      [10:12:02,214,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean sessionLog with id = 1016095940932 - Cache size = 1
      [10:12:56,276,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domain with id = com.opensugar.manager.admin.domains.DomainPK@6d86c3ed - Cache size = 2
      [10:12:56,276,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domain with id = com.opensugar.manager.admin.domains.DomainPK@249724 - Cache size = 1
      [10:13:13,667,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domainsApplications with id = com.opensugar.manager.admin.relations.domainsApplications.DomainsApplicationsPK@1710fc9c - Cache size = 5
      [10:13:13,667,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domainsApplications with id = com.opensugar.manager.admin.relations.domainsApplications.DomainsApplicationsPK@16c45acd - Cache size = 4
      [10:13:13,667,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domainsApplications with id = com.opensugar.manager.admin.relations.domainsApplications.DomainsApplicationsPK@b3213dc0 - Cache size = 3
      [10:13:13,667,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domainsApplications with id = com.opensugar.manager.admin.relations.domainsApplications.DomainsApplicationsPK@c27f2f36 - Cache size = 2
      [10:13:13,667,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean domainsApplications with id = com.opensugar.manager.admin.relations.domainsApplications.DomainsApplicationsPK@7ec0f677 - Cache size = 1
      [10:13:49,995,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean user with id = com.opensugar.manager.admin.users.UserPK@f74439be - Cache size = 3
      [10:13:49,995,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean user with id = com.opensugar.manager.admin.users.UserPK@14a5af3 - Cache size = 2
      [10:13:49,995,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean user with id = com.opensugar.manager.admin.users.UserPK@f61bc0c4 - Cache size = 1
      [10:14:12,542,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean group with id = com.opensugar.manager.admin.groups.GroupPK@f61bc0c4 - Cache size = 4
      [10:14:12,542,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean group with id = com.opensugar.manager.admin.groups.GroupPK@dcba85fe - Cache size = 3
      [10:14:12,542,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean group with id = com.opensugar.manager.admin.groups.GroupPK@14a5af3 - Cache size = 2
      [10:14:12,542,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean group with id = com.opensugar.manager.admin.groups.GroupPK@f74439be - Cache size = 1
      [10:14:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@b98aba6d - Cache size = 5
      [10:14:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@455f7b1e - Cache size = 4
      [10:14:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@4512d94f - Cache size = 3
      [10:14:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@3648f5e7 - Cache size = 2
      [10:14:52,464,LRUEnterpriseContextCachePolicy] Scheduling for passivation overaged bean groupsApplications with id = com.opensugar.manager.admin.relations.groupsApplications.GroupsApplicationsPK@35fc5418 - Cache size = 1



      =========================================================What should I understand ??????
      All my transaction attribute are Required .....
      Should I change ome of them ????

        • 1. Re: TRANSACTION ROLLBACK EXCEPTION
          jeffdelong

          I am seeing this same exception in this same configuration when I try to access a stateful session bean from a jsp. Have you determined the cause or found a workaround?

          In the same scenario I also saw exceptions related to concurrent access to the bean. The jsps hold the bean reference in the session scope, and multiple frames may use the bean, possibly concurrently, which the spec does not allow. Is there a way in JBoss to control this? (weblogic has an attribute in the weblogic-ejb-jar.xml (allow-concurrent-access) that addresses this for example.

          Could these exceptions be related?

          • 2. Re: TRANSACTION ROLLBACK EXCEPTION
            jeffdelong

            I modified my jsps to avoid the concurrent access exceptions, but still see the transaction rollback exception.