Hi,
I had this situation once few years ago.
I was working and I discovered that the pool was exhausted to access
Oracle and the application stucked.
It was really tricky to find the error because nothing indicates a problem.
The explanation was this one : A dynamic query (created in java) doing
some imbricated requests froze the database access.
So the query was never ending, waiting for a new connection to continue
requesting ... and so on.
Lionel
Ice72 wrote:
Yes ... in theory. But if was this case, in the jstack dump, we should view
the incoming http-req
which waiting for a pooled connection (I have a ConnPool.getConnection()
class/method).
But ... on the dump there is anything ... P-(
Christopher Schultz-2 wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ice,
Ice72 wrote:
Hi Cris,
thanks for your reply. Yes: I checked the process via top/netstat/lsof
and I
haven't detect any
strange situation. The super-strange thing is that the other webapps, on
the
same tomcat-instance,
continue to work when the single-app fail.
Sounds like a db connection pool exhaustion.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG3cFx9CaO5/Lv0PARAqwEAJ9G2/L/Id9b3igPx/F4AVWfqxfAMQCfTlBy
g8sHhqlF2PBWGDhx0ZSmwq4=
=j3zb
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
