justinphillips
Programmer
I am having a problem with tying up JMS queues with JDBC work within a single transaction. I am getting a 'UserTransaction' from the application server using JNDI. Also I get a TXDataSource and the JMS objects needed via JNDI.
I call the UserTransaction.begin() method, and perform the JMS and JDBC work. When finished, I then call UserTransaction.commit(). At this point, the message appears on the JMS with no problems, and it definately taking part in the transaction. However, the JDBC updates are not. The connection is fine, as I have called commit on the connection and the updates work. It is not being tied in with the transaction.
Here are some points to note:
1) I am using WL 6.1 SP4, and Oracle 8.1.7
2) I using the 'oracle.jdbc.xa.client.OracleXAConnection' which within the connection pool, which the TXDataSource is pointing to
3) If I use the 'oracle.jdbc.xa.client.OracleXADataSource' driver, it wont return any result sets, and just hangs. This is the driver the BEA examples use.
Any ideas?
Thanks
Justin Phillips
I call the UserTransaction.begin() method, and perform the JMS and JDBC work. When finished, I then call UserTransaction.commit(). At this point, the message appears on the JMS with no problems, and it definately taking part in the transaction. However, the JDBC updates are not. The connection is fine, as I have called commit on the connection and the updates work. It is not being tied in with the transaction.
Here are some points to note:
1) I am using WL 6.1 SP4, and Oracle 8.1.7
2) I using the 'oracle.jdbc.xa.client.OracleXAConnection' which within the connection pool, which the TXDataSource is pointing to
3) If I use the 'oracle.jdbc.xa.client.OracleXADataSource' driver, it wont return any result sets, and just hangs. This is the driver the BEA examples use.
Any ideas?
Thanks
Justin Phillips