Oops, I think I must revise my last comment.
It looks like it only takes some more time until the exception "
java.sql.SQLException: Connection.close() has already been called.
Invalid operation in this state." occurs.
However I don't see anymore "org.exolab.castor.jdo.PersistenceException:
This thread is already associated with a transaction in progress"
exceptions.
Resultsets are now closed in finally blocks - what about the OQLQuery
objects? Do they need to be closed aswell?
Whatelse could be a leak ?
Jens
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
