Simulated distributed transactions in WLS5.1

Question

Hello
          I can´t use WLS 6.0 I must use WLS 5.1. So I can´t to use distributed
          transactions.
          So that, my problem is this situation:
          Client code: in WL Personalization Server
          method
          UserTransaction.begin
          class1.create
          class2.updateDatabaseOracle1
          this.comit();
          Exception
          this.rollback();
          method commit
          class1.commit();
          class2.commit();
          UserTransaction.commit
          methdo rollback
          class1.rollback;
          class2.rollback;
          UserTransaction.rollback
          class1 in WL Personalization Server
          create
          EJBCreate
          commit
          EJB.putData
          rollback
          EJB.remove
          EJB in WL5.1
          I get this Error:
          "Connection has already been created in this tx context for pool
          named pool1. Illegal attempt to create connection from another
          pool: pool2"
          Can I modify the type of transaction in the EJB that solve this error??
          if the request is false How can I simulated it?
          I can lose the transanction because my class (class1) implements a
          rollback and commit methods that save it.
          Please Help
          Miguel Lopez Montero
          Soluziona Servicios Internet,Spain
          

Answer 1

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC_TX ():
In the readme file of Oracle JDBC drivers 8.1.6.0.1 (http://technet.oracle.com/software/tech/java/sqlj_jdbc/files/Readme_01.txt)
it mentioned that it supports "distributed transactions".
As I understand, JDBC transaction is connection based and uses Oracle internal transaction manager. In order to do "distributed transactions", I must have at least two connections open at the same time each to its own database instance. How does the two connections coordinate the transactions? I thought in order to support "distributed transactions", one has to build a higher layer to encapsulate the two connections and therefore coordinate the distributed transactions. Any examples will be welcome.<HR></BLOCKQUOTE>
The two branches of the transaction are coordinated using 2-phase commit.
For samples look under
$ORACLE_HOME/jdbc/demo/samples/oci8/jdbc20-samples/
null