You put the code in DatabaseStorageManager.releaseActiveConnection() method. Maybe this is more appropriate, but in this way it is still possible that another class returns a connection to the pool with the autocommit set to false. Personally I think that putting the code in MultiConnection.close() or MultiPool.putBack() is more robust.
Well, I have the intention to take a good hard look at MultiConnection and MultiPool, and how they work. Also, this might not solve issues with other connection pooling code (such as datasources retrieved from the appserver).
And I don't know which other class would do this? Afaik no other classes set autocommit.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
