Tomcat is crashing every 2 - 3 days on 2 different Linux machines.
Both machines are running pretty much identical software configurations.
Both machines are serving the same web application so, it's almost certainly
something in my web app code that causes the problem. However; the logs from my
:24 AM
To: Tomcat Users List
Subject: Tomcat Crashing on Linux
Tomcat is crashing every 2 - 3 days on 2 different Linux machines.
Both machines are running pretty much identical software
configurations.
Both machines are serving the same web application so, it's almost
certainly
something in my web
Also,
The only way I can clear this error is to reboot the machine.
Here is another piece of info I get from catalina_log.2003-07-29.txt when I
try the 2nd restart (/etc/init.d/tomcat restart)
2003-07-29 11:06:33 JDBCRealm[Standalone]: Exception closing database connection
java.sql.SQLException:
ChemInformatics
-Original Message-
From: Rick Roberts [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 11:24 AM
To: Tomcat Users List
Subject: Tomcat Crashing on Linux
Tomcat is crashing every 2 - 3 days on 2 different Linux machines.
Both machines are running pretty much identical software
I had not seen this problem before I recently started implementing JDBCRealm on
these servers.
Anyone else having stability problems when using Oracle JDBCRealm?
Rick Roberts wrote:
Also,
The only way I can clear this error is to reboot the machine.
Here is another piece of info I get from
Hi,
Check to make sure you aren't throwing a lock down somewhere and stacking
up threads behind it.
-e
On Tue, 29 Jul 2003, Rick Roberts wrote:
I had not seen this problem before I recently started implementing JDBCRealm on
these servers.
Anyone else having stability problems when using
I thought that the new threading stuff in the RH9 kernel caused problems
with the JVM and native threads.
At 12:25 29/07/2003 -0400, you wrote:
Hi,
Check to make sure you aren't throwing a lock down somewhere and stacking
up threads behind it.
-e
On Tue, 29 Jul 2003, Rick Roberts wrote:
I
You might want to look at how many processes/threads are listed for tomcat
and your database.
You might see that one of them or both is creating and keeping too many
threads around. At least that would be a start.
For tomcat, I have a daemon script that has a status command that tells
you all
You are correct. Crashing is the wrong way to describe it.
There is a process still active in my process list.
This has become frequent enough that I should be able to track it down.
However; I don't know what triggers the failure. I only know that it happens
every few days on both computers.
Earlier today we were talking about thread dumps. You might want to
generate some next time this is happening. It will show you if a thread
is locked and what it is waiting on.
send a kill -QUIT to the VM when it is hanging. It's often a good idea to
get like 5 or 6 thread dumps right in a row
Another thing that I do during development, with only myself accessing the
site, is do things on the website that will require a database connection.
I keep doing them over and over, and if more database connections are
created I know something is wrong. Because since I'm the only one
11 matches
Mail list logo
