Help needed - transaction atomicity did not happen

Question

          Hi -
          We recently encountered a strange problem. Due to a bad search query in another
          application, our Oracle RDBMS was running our of SGA and causing transactions
          to fail.
          What makes us worry more is that we had transactions spanning 2 entity beans part
          committed and part rollbacked! The following scenario describes:
          In a single method XX within a Session Bean facade, we have
          call entity bean A to create (CMP, transaction REQUIRED)
          call entity bean B to create (CMP, transaction REQUIRED)
          .some logging info here at point 1
          From our debug log, the program cleary runs to point 1. And the data written
          by entity bean B was committed and found in database. But the one written by
          entity Bean A is NOT! There is an exception for rollback in the log.
          Q1. How does container commit work? Can an execution continue till the return
          of method XX before the container tries to commit and get an error?
          Q2. Also, why isn't the whole transaction rollbacked? What are we missing?
          We are using TxDataSource, and db driver is weblogic.jdbc.oci.Driver.
          Any help and pointer appreciated. Thanks!
          ph
          

Answer 1

Sounds as if your session facade method XX does not open a transaction.
          Then you have two transactions, A and B, which can be rolled back or
          committed independent of each other.
          Try setting transaction required for the method XX.
          Also, in the entity beans, you can use
          weblogic.transaction.TxHelper.getTransaction().getName() or getXid() to
          find out if A and B use the same transaction or different ones.
          Philip
          Pow-hwee Tan wrote:
          > Hi -
          >
          > We recently encountered a strange problem. Due to a bad search query in another
          > application, our Oracle RDBMS was running our of SGA and causing transactions
          > to fail.
          >
          > What makes us worry more is that we had transactions spanning 2 entity beans part
          > committed and part rollbacked! The following scenario describes:
          >
          > In a single method XX within a Session Bean facade, we have
          >
          > call entity bean A to create (CMP, transaction REQUIRED)
          > call entity bean B to create (CMP, transaction REQUIRED)
          > .some logging info here at point 1
          >
          > From our debug log, the program cleary runs to point 1. And the data written
          > by entity bean B was committed and found in database. But the one written by
          > entity Bean A is NOT! There is an exception for rollback in the log.
          >
          > Q1. How does container commit work? Can an execution continue till the return
          > of method XX before the container tries to commit and get an error?
          >
          >
          > Q2. Also, why isn't the whole transaction rollbacked? What are we missing?
          >
          > We are using TxDataSource, and db driver is weblogic.jdbc.oci.Driver.
          >
          > Any help and pointer appreciated. Thanks!
          >
          > ph
          >