I experienced a lot of confusion and frustration on this same issue.
I don't know the exact answer for you, but I found my Torque
connections were less troublesome if I tested if Torque was
initialized before calling Torque.init(). I think that might address
a different problem but this is worth a try!
if ( ! Torque.isInit() )
{
Torque.init();
}
Hi,
I've configured Torque in a web application, under Tomcat 4.1. The
Torque.init() command is succesfully issued from a Context listener
class (in the contextInitialized method).
If I reload the webapp from the Tomcat Manager, the listener
re-issues the Torque.init() apparently without problems, but every
database operation fails with a TorqueException saying that the
Connection object is null. That is given after the IDBroker thread
has been started.
Restarting Tomcat completely makes the webapp working again.
Any hint about this issue ?
I'm using Torque decoupled 3.0.1, JDK 1.3.1_07.
Thanks in advance.
--
Giulio Vezzelli
Infolog S.r.l.
Web : http://www.infolog.it
E-mail : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
