Session management in session bean calling session bean

Question

Hi,
          I've got another question on transaction.
          I have following stateless session beans :
          session1 with trans-attribute Required.
          session2 with trans-attribute Required.
          session1 calls session2 and session3.
          session2 inserts/updates records in the database.
          What am doing is first I call a createSchedule method in session2, which
          creates a new record in the database.
          And then I call an update method on the session2 bean, that will fetch and
          update the newly created record.
          This second update fails, due to some database constraints.
          What I was hoping, that the record should not be created in the database,
          but it did.
          The first method call in session2 succeeded and the second failed !!
          Doesnt both the DML be part of one transaction ?
          Thanks
          Amit
          

Answer 1

Solved this one too :
          What was happening was, Before I called the create method of the session
          bean, I was calling a find method, and I was capturing the exception, and in
          case theres an exception, assuming that there is no record in the database,
          I create a new record. This find method is in the same session bean,
          session2 along with the create and update methods. Inititally when there was
          no record, the session bean was raising EJBException, due to which the main
          session bean, session1, rollbacks the transaction, it started, but as I was
          catching this exception, so the execution continued, .... next statement
          being create, and as the transaction attribute of it was Required, and as
          the session1 bean's transaction has already been rolled back, there was no
          transaction, so the create method started its own transaction, and created
          the record, and then the update method too did the same, but it gave an
          error, so only update method's transaction got rolled back.
          So I changed the find method to throw FinderException, instead of
          EJBException, so the transaction of sessio1 bean is not lost.
          Its working now.
          But the other problem I posted, where I dont want to throw any exception to
          the client calling the session1 bean, I still havent figured it out, how to
          stop it, although am catching all the exceptions, still the client got
          exception.
          Thanks
          Amit Chauhan
          eTouch System
          510-795-4800 ext 113
          Amit <[email protected]> wrote in message
          news:[email protected]...
          > Hi,
          > I've got another question on transaction.
          > I have following stateless session beans :
          > session1 with trans-attribute Required.
          > session2 with trans-attribute Required.
          >
          > session1 calls session2 and session3.
          >
          > session2 inserts/updates records in the database.
          >
          > What am doing is first I call a createSchedule method in session2, which
          > creates a new record in the database.
          > And then I call an update method on the session2 bean, that will fetch and
          > update the newly created record.
          >
          > This second update fails, due to some database constraints.
          > What I was hoping, that the record should not be created in the database,
          > but it did.
          > The first method call in session2 succeeded and the second failed !!
          >
          > Doesnt both the DML be part of one transaction ?
          >
          > Thanks
          > --
          > Amit
          >
          >
          >