Help-Problem in calling JMS inside an EJB having transaction attribute Required New

Question

          Hi,
          Version wl 5.1 service pack 8
          OS - unix
          I am using a Container managed bean say Bean1(transaction attribute Required)
          which in one of its method is trying to call another EJB say Bean2 which has the
          transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
          JMS funtions coded to persist to database.JMS uses Queue connection factory and
          is an non transaction JMS session.The JMS server is running in a separate weblogic
          server and not in the server where EJB is deployed.I use the url of the JMS server
          and get the context of that server and connect my JMS.
          The problem that i am facing is
          I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
          and i can see the JMS doing the insert in the table and everthing works fine.But
          after few seconds i can see the exception/message seen on the console of the weblogic
          server where my JMS server is running as below
          Tue Sep 04 15:57:09 CDT 2001:<I> <TX> Transaction (TxC (30486015, xid = 99963563
          2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
          .110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
          After this happen i dont see any roll back in either bean1 or bean2 or the JMS
          insert is rolled back.
          I don't know why this exception is thrown and no effects on the rollback and it
          works the way i wanted.But the only thing that keeps bothering me is the rollback
          and why does this happen.
          Thanks
          Krish.
          

Answer 1

The exception your seeing is troubling - if the tran is rolled
          back than whatever work is associated should also roll back. I suggest
          instrumenting your code to see if the tran rolling back is the same tran
          that is being used for the transactional application work that appears to succeed.
          Also, try forcing a rollback, you may see that the EJB work truly rolls back
          while the JMS work does not.
          I'm not really familiar with 5.1, but I know there is a fundamental limitation to one
          phase commits, this means that the JDBC connection pool used by JMS as well
          as that used by the EJB must be one and the same - I'm not exactly sure how
          it works, but I'm pretty sure multiple servers can share the same connection pool.
          This post seems unrelated to clustering, if you need further help, I
          suggest posting in the ejb or transaction newsgroups.
          Krish wrote:
          > Hi,
          >
          > Version wl 5.1 service pack 8
          > OS - unix
          >
          > I am using a Container managed bean say Bean1(transaction attribute Required)
          > which in one of its method is trying to call another EJB say Bean2 which has the
          > transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
          > JMS funtions coded to persist to database.JMS uses Queue connection factory and
          > is an non transaction JMS session.The JMS server is running in a separate weblogic
          > server and not in the server where EJB is deployed.I use the url of the JMS server
          > and get the context of that server and connect my JMS.
          >
          > The problem that i am facing is
          >
          > I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
          > and i can see the JMS doing the insert in the table and everthing works fine.But
          > after few seconds i can see the exception/message seen on the console of the weblogic
          > server where my JMS server is running as below
          >
          > Tue Sep 04 15:57:09 CDT 2001:<I> <TX> Transaction (TxC (30486015, xid = 99963563
          > 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
          > 110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
          >
          >
          > After this happen i dont see any roll back in either bean1 or bean2 or the JMS
          > insert is rolled back.
          >
          > I don't know why this exception is thrown and no effects on the rollback and it
          > works the way i wanted.But the only thing that keeps bothering me is the rollback
          > and why does this happen.
          >
          > Thanks
          >
          > Krish.