Re: JTA transaction on 2 datasources....

On 10/17/2001 at 07:51:07 AM, java400-l-admin@midrange.com wrote:
I've got a problem using two cmp entity beans of different containers in
one transaction. The containers have different  datasources. A session
bean starts the transaction. The isolation level of all beans is
TRANSACTION_REPEATABLE_READ. Both entity beans have the transaction
attribute TX_SUPPORTS. The invoked method of the session bean has
TX_REQUIRES_NEW. Always the session bean wants to create an entity bean in
a different container an exception occurs. The jdbc driver is
"com.ibm.db2.jdbc.app.DB2Driver" and jta is enabled. If both containers
have the same datasource (and the tables are moved to the other
collection) all works fine.

Has anyone an idea why the JTA two phase commit doesn't work?
--- end of excerpt ---

Can you get us a little more detail?
Is the exception a websphere, JDBC or JVM exception?
Show us the stacks? Output logs or JDBC trace?

JDBC trace is done in Websphere by putting these things
in the command line of the application server that runs your
application. Start it, run your test, and stop it as
quickly as possible (the trace gets _really_ big otherwise).

App server command line:
-Djdbc.db2.trace=3
-Djdbc.db2.cli.trace=true
-Djdbc.db2.trace.config=file:///jdbc.%j.txt

(this trace.config setting outputs the jdbc trace in output
file "/jdbc.<jobname>.txt" where jobname is... well... the job name.


In every single ethnic, religious or racial group, there are a
very few truly evil people. For each of those people there
are many, many, many good people.
Assuming anything (evilness or capability for evil) about the
particular group is bigotry and idiocy. Don't do it.  -- Me

Fred A. Kulack  -  AS/400e  Java and Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN  (Phone: 507.253.5982   T/L 553-5982)
mailto:kulack@us.ibm.com   Personal: mailto:kulack@magnaspeed.net
AOL Instant Messenger: Home:FKulack  Work:FKulackWrk