Donn,
It looks like the total files opened are less than 1,000 and the ulimit is
set to 4,096 (this was increased as a way to check if ulimit was a
problem... did not change the behavior of the system.)
We use jdbc with the commons pooling process. We follow the number of open
connections very closely (logging to catalina.out) because we have had
connection leaks (still have a small one) in the past.
We do not use LDAP.
Thanks,
Carl
----- Original Message -----
From: "Donn Aiken" <[email protected]>
To: "Tomcat Users List" <[email protected]>
Sent: Friday, February 12, 2010 4:00 PM
Subject: Re: Tomcat dies suddenly
Carl -
I did have something like this happen to me - not with Tomcat but with
another JEE container. The container would run for a while, without
incident, then suddenly simply die, with nothing in any log, and not on any
apparent time schedule.
We had some code that was manipulating LDAP that had a leak in it. For each
leaked connection, we had an open file descriptor that never went away,
until the process went away. If memory serves, we finally found it by
looking at entries in /proc/{pid of jvm}/fd, doing a bunch of find . | wc
and watching that over time.
I hope this is of some help. Good luck.
Donn
On Fri, Feb 12, 2010 at 3:46 PM, Carl <[email protected]> wrote:
Andre,
Take my comment as a compliment because that is the way it was meant...
you
have helped a lot of people on this least and I, for one, really
appreciate
that.
I was waiting to see if someone could give me an idea how to implement
what
you remembered and, if not, then I would google around to see if I could
find it myself.
Thanks,
Carl
----- Original Message ----- From: "André Warnier" <[email protected]>
To: "Tomcat Users List" <[email protected]>
Sent: Friday, February 12, 2010 3:34 PM
Subject: Re: Tomcat dies suddenly
Carl wrote:
Andre,
Thanks for the response.
I have read almost all of your posts and realy enjoy the way to take
problems apart.
Keep on thinking.
I'm not quite sure how to take the above answer..
So, just in case, and maybe to my own ultimate embarassment, I want to
indicate that I was serious. I seem to remember cases where an
application
at the point of dying, would have very much liked to log a last desperate
message to indicate the situation, but did not even have the resources
left
to be able to do so.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
