I have two Java Stateless Session Beans with CMT running on different
boxes being controlled by the same TransactionManager.
Each aquires a JDBC connection through JNDI to a
org.apache.derby.jdbc.ClientXADataSource which points to the same
physical networked Derby server instance - i.e. the connection URL is to
the same machine and port; jdbc:derby://dbserver:1527/ExperimentDB
The first bean inserts some data into a table and then calls the second
bean on a different box which attempts to find the data which has just
been inserted.
My question is IFF the TransactionManager has propgate the transaction
context correctly to the second box so the second bean is participating
in the same global distributed transaction, will Derby allow the second
bean on a different box to 'see' the uncommited data which is part of
the distributed transaction?
I only ask as I cannot and assume that it is because I have not set up
the TransactionManager/Cluster correctly, if Derby cannot 'possibly'
make the changed data available to the second transaction then I am
wasting my time.
Thanks.
- Distributed Txns across 2 processes/machines JF
-