Some connection pools have 'ping' functionality for connections, some don't. Depends on the pool you are using ;) I think DBCP has this option but we're not using it so I can't be sure...
HTH,
Jon
Sonny Sukumar wrote:
Interesting observation. I think you might be onto something, but let's explore it a bit further.
I'm using DBCP with a MySQL backend database. I don't really get why Tomcat would stop responding though after several hours of idle time though. You think it's because after all those hours of idle time the # of db connections is 0? I thought the connection pool could handle that and create a new connection when needed.
I think I'm not understanding though...do enlighten me. :-)
Thanks for your help,
Sonny
--- mike jackson <[EMAIL PROTECTED]> wrote:
---------------------------------------------------------------------When this has happened to me it's usually been the database connection pool that I'm using. Or was using. If it looks like you had a bunch of connections prior to the restart and very few after then you've found your culprit. You database should be able to give you a connection count, but the way to get it depends on the database so I can't help you there.
--mikej -=------ mike jackson [EMAIL PROTECTED]
-----Original Message----- From: Sonny Sukumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 3:25 PM To: [EMAIL PROTECTED] Subject: Tomcat mysteriously stops responding...
Hey guys,
I've had the persistent problem with Tomcat (using Cocoon) over some months now where when I go to
bed at
night my Tomcat/Cocoon server is functioning just
fine
and I can access all web pages, both static and dynamically generated (from a backend db).
But when I wake up and try to access the pages the connection just times out and I get a totally
blank
response. This doesn't happen every single day,
but
often enough to be annoying. We're soon going
live
with the site, so this happening **at all** is a
scary
thought. I can't seem to figure out what the
problem
could be.
I'm fairly sure it's Tomcat because restarting
Tomcat
almost always solves the problem. I've had this problem through all my Tomcat upgrades (4.1.12 all
the
way to 4.1.27 now) and my Cocoon upgrades (from
2.0.x
all the way until latest 2.1.2).
Has anybody else experienced this? Any idea what
it
could be?
Thanks!
Sonny
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product
search
http://shopping.yahoo.com
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]
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
--------------------------------------------------------------------- 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]
