tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Maltby <>
Subject RE: JDBC Error
Date Fri, 28 Jun 2002 14:33:09 GMT


I am using a connection pool manager from BitMechanics (
).  The sequence if my handleRequest( .. ) is to call the connection pool
manager to get a connection, run the processQuery ( .. ), and then finally
issue close().

Sound right?  Do you have a connection manager that you would recommend?


-----Original Message-----
From: Ralph Einfeldt []
Sent: June 28, 2002 10:20 AM
To: Tomcat Users List
Subject: AW: JDBC Error

It depend on how you use your connection.

If you open it and hope that sending any command to the 
connection might reopen it if it's closed, that won't 

It's in general not a recommended solution to keep 
connections open for the lifetime of a session.

You should get/release the connection with every request.
To avoid performance penalties you should use a connection

> -----Ursprungliche Nachricht-----
> Von: Roger Maltby []
> Gesendet: Freitag, 28. Juni 2002 15:16
> An: 'Tomcat Users List'
> Betreff: RE: JDBC Error
>   - it would time out since I have ended my session with the 
> Linux system (no other users connected), I can leave it for 
> 5-10 minutes with no problem
>   - that when I start-up my browser from my NT system and the 
> Servlet issues JDBC connection it would then reconnect

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message