close fails on database connections (managed connection cleanup fails) in websphere 7 but not in web

Posted by mete on Stack Overflow See other posts from Stack Overflow or by mete
Published on 2010-04-11T08:19:30Z Indexed on 2010/04/11 8:23 UTC
Read the original article Hit count: 375

I have a simple method (used in a web application through servlets) that gets a connection from a JNDI name and issues a select statement (get connection, issue select, return result, close the connection etc. in finally). Due to other methods in the application the connection is set as autocommit=false. This method works normally in websphere 6.1 as well as in glassfish and weblogic. However, in websphere 7, it receives cleanup failed error when I close the connection because, it says, the connection is still in a transaction. Because I was not updating anything I did not commit or rollback the connection in this method (which can be wrong). If I add commit before closing the connection, it works. My question is why it works in websphere 6.1 (and other containers) and why not in websphere 7 ? What can be the cause of this difference ?

© Stack Overflow or respective owner

Related posts about database-connection

Related posts about websphere