Container managed transaction problem


EJB programming & troubleshooting: Container managed transaction problem

  1. Container managed transaction problem (3 messages)

    Hi guys,

    I wanted to know if any of you guys might have any idea on this problem that I am facing.

    I am using Weblogic 6.1 SP2 on Oracle I have a stateless session bean that calls another SLSB. The second SLSB does some database operations. When an exception is raised after the database operations, the exception was propagated to the calling SLSB. The stack trace showed the TransactionRolledBackException was thrown. When checked against the database, all the db operations were committed. The same was tested on Oracle 8.1.6 and was working fine.

    Thanks in advance.
  2. These kinds of problems seem to come from two things,

    (i) Not using a Tx data source
    (ii) The driver having auto commit turned on.

    I would check both,
  3. Thanks for the reply. I am using TxDataSource and since it is a container managed transaction, it is the container which sets the autoCommit flag, and ultimately commits or rolls back the transaction. I was wondering if any of you guys encountered this problem in oracle 9i. It is actually working fine for 8i.

    Is there anything I need to do on the database side?
  4. You can check for the Auto commit option in the Oracle9i
    that might be enable