I should add that your app should use the connection and the throw it back
in the pool rather quickly. Upping the connections might fix it or
prolong the inevitable errors. You should really find out why you are not
releasing the connections.
It is possible you could just have so much traffic
Hi,
Your pool of connections to your database is exhausted. Try upping the
number.
-e
On Fri, 8 Aug 2003, Barclay A. Dunn wrote:
we are getting a ton of these errors in our catalina.out and i could use
help in fixing it.
i know they are related to our connection pooling, but not what to
I'm pretty sure can't create socket means it can't connect to the DB for
some reason. I would wager the DB (or something) is refusing the
connection. The fact that it said can't create socket means that tomcat
is trying to do so. So that part of it seems alright.
-e
On Fri, 8 Aug 2003,
Sorry, I sent this a little to soon...
Get 5 or 10 thread dumps in a row real fast... just bam, bam, bam, etc...
From that you can tell what the threads are doing. They should be moving
through methods (or classes) very quickly. If they are sticking they are
waiting on something and that's
Hi,
Do a ps -ef (or ps -aux) and find out the PID of the java process (your
sys-admin can help here). Then do a 'kill -QUIT PID' where PID is the
PID of the java process.
It will send the thread dump to the catalina.out file.
Deciphering the thread dump is a little difficult if you have never
Is it also unlimited (or insanely huge) on the database?
-e
On Fri, 8 Aug 2003, Barclay A. Dunn wrote:
i adjusted the pool to unlimited and am still getting these errors.
something else seems to be fekachte.
barclay
-Original Message-
From: Eric J. Pinnell [mailto:[EMAIL
Hi,
You could get a thread dump and see where your connections are hanging.
When you get your errors kill -QUIT the pid.
-e
On Fri, 8 Aug 2003, Barclay A. Dunn wrote:
ok, well, at least we have concrete proof of it.
now, given that i can confirm that i am closing connections (calling
