Websphere 5.0 and non-jts-datasource = 2PC exception!

Question

Hello all
We're migrating from a working weblogic 8 app to websphere 5.0, and we run into this problem.
Toplink tries to enlist the NON-JTS datasource in the global transaction. In weblogic we defined our non-jts datasource as a non-transactional datasource, but there is no such option in websphere. What is going on??
Please help
TIA
- Russ -

Answer 1

Hello Rustam,
WebSphere 5 throws exceptions when you try to get a non-jta datasource while in a transaction - it seems to try to enlist it in the transaction I think.
This is more a WebSphere issue, since it means you cannot read outside of the transaction.
There are 3 options:
1) Don't define a non-jta datasource at all in TopLink. Draw backs to this are that there may be problems reading when there is no transaction, such as when you are using cache synch.
2) Create your own datasource (outside of WebSphere) and place it in JNDI. Then have TopLink access it as a non-jta datasource. Your datasource must be completely independent of WebSphere so that it does not attempt to associate with JTA.
3) Use a TopLink maintained read connetion pool. You can use the non-jts-connection-url sessions.xml tag, which will use the login setting defined in your project.xml. I've not tested it, but can also override the read pool in a preLogin event that should look something like:
public void preLogin(SessionEvent event) {
DatabaseLogin dbLogin(new Oracle9iPlatform());
dbLogin.setUserName("name");
dbLogin.setPassword("password");
dbLogin.setConnectionString("jdbc:oracle:thin:@ip:port:sid");
ConnectionPool readPool = new ReadConnectionPool("read", dbLogin, minCon, maxCon, event.getSession());
event.getSession().setReadConnectionPool(readPool);
Best Regards,
Chris Delahunt