Can't serialize access for this transaction error.

Question

Hi,
          I am getting a transaction rolled back due to a beforeCompletion exception:
          java.sql.SQLException: ORA-08177: can't serialize access for this
          transaction
          I am using Weblogic 5.10, SP5 & Oracle 8.
          Basically what I have is:
          - A java app that will get an EntityBean, named Schedule.
          - The java app will then create a SessionBean, named Watchdog.
          - The java app will then call a method on the Watchdog, passing in the
          Schedule: watchdog.check(Schedule sched)
          - The watchdog.check() method will do some processing and based on the
          outcome may or may not update the Schedule: sched.setLast(<some number>)
          - The check() method is then done & return to the java app.
          I see log messages (on the weblogic server) saying the check() method is
          done. Then I see messages, presumably from the container for:
          - isModified ------> true
          - ejbStore()
          And then I see the exception messages.
          The strange thing is that most of the time this processing works just fine.
          Only occasionally do these exceptions get thrown.
          The schedule EntityBean is set up as <transaction-isolation> for
          TRANSACTION_SERIALIZABLE.
          There is no other bean trying to update the Schedule at the same time.
          Does anybody have any ideas?
          Thanks in advance,
          Beth
          

Answer 1

http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#107296
          8
          tells u about the limitations of transaction_serializable w.r.t. Oracle..
          Pavan
          "Beth" <[email protected]> wrote in message news:[email protected]...
          > Hi,
          >
          > I am getting a transaction rolled back due to a beforeCompletion
          exception:
          > java.sql.SQLException: ORA-08177: can't serialize access for this
          > transaction
          >
          > I am using Weblogic 5.10, SP5 & Oracle 8.
          >
          > Basically what I have is:
          > - A java app that will get an EntityBean, named Schedule.
          > - The java app will then create a SessionBean, named Watchdog.
          > - The java app will then call a method on the Watchdog, passing in the
          > Schedule: watchdog.check(Schedule sched)
          > - The watchdog.check() method will do some processing and based on the
          > outcome may or may not update the Schedule: sched.setLast(<some number>)
          > - The check() method is then done & return to the java app.
          >
          > I see log messages (on the weblogic server) saying the check() method is
          > done. Then I see messages, presumably from the container for:
          > - isModified ------> true
          > - ejbStore()
          > And then I see the exception messages.
          >
          > The strange thing is that most of the time this processing works just
          fine.
          > Only occasionally do these exceptions get thrown.
          >
          > The schedule EntityBean is set up as <transaction-isolation> for
          > TRANSACTION_SERIALIZABLE.
          > There is no other bean trying to update the Schedule at the same time.
          >
          > Does anybody have any ideas?
          > Thanks in advance,
          > Beth
          >
          >
          >
          >