Re: Tomcat windows service terminated expectedly

2006-06-05 Thread Bill Tomlinson

On 6/3/06, Martin Gainty [EMAIL PROTECTED] wrote:

Good Morning Bill-

I agree this can be a bit of a challenge but I found starting with base
webapps and then adding one webapp at a time usually helps
Also in the server.xml turn on debug flag via debug attribute
Server port=PutDefaultPortNumberHere debug=1
Then check the Logs and send that to us here


The documentation for server doesn't say anything about a debug attribute
(http://tomcat.apache.org/tomcat-5.5-doc/config/server.html).

So I wanted to verify that this attribute is correct. And is there any
documentation about this attribute (what the debug levels are and
where the output goes).



- Original Message -
From: Bill Tomlinson [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Friday, June 02, 2006 12:07 PM
Subject: Tomcat windows service terminated expectedly


 We're running tomcat in standalone mode as a windows service. Every
 once and a while tomcat crashes with no logs or errors. Just not
 running anymore. The windows event log just says service terminated
 unexpectedly. The tomcat service can be restarted without problems.
 We haven't been able to determine any pattern to these failures,
 either in time or in usage. And we can't reproduce it on demand.

 We have two different installations, and both see this problem:
 Installation 1:
 Windows 2000 Server
 Java 1.4.2
 Tomcat 5.0.18
 Installation 2:
 Windows 2003 Server
 Java 1.5.0
 Tomcat 5.5.16

 I realize that this isn't much to go on, and I apologize for that. But
 what I'm really looking for is just some information about what we
 could possibly be doing in our web application that would cause tomcat
 to crash with no logs (aside from calling System.exit(), I did check
 that).

 Maybe if I present it as a challenge it will get someone's interest.
 Challenge: write a servlet that crashes tomcat (running as a windows
 service) without generating any logs!

 I'm just looking for any hints about what areas I whould be looking into.

 Thanks.

 -
 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]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Tomcat windows service terminated expectedly

2006-06-02 Thread Bill Tomlinson

We're running tomcat in standalone mode as a windows service. Every
once and a while tomcat crashes with no logs or errors. Just not
running anymore. The windows event log just says service terminated
unexpectedly. The tomcat service can be restarted without problems.
We haven't been able to determine any pattern to these failures,
either in time or in usage. And we can't reproduce it on demand.

We have two different installations, and both see this problem:
Installation 1:
Windows 2000 Server
Java 1.4.2
Tomcat 5.0.18
Installation 2:
Windows 2003 Server
Java 1.5.0
Tomcat 5.5.16

I realize that this isn't much to go on, and I apologize for that. But
what I'm really looking for is just some information about what we
could possibly be doing in our web application that would cause tomcat
to crash with no logs (aside from calling System.exit(), I did check
that).

Maybe if I present it as a challenge it will get someone's interest.
Challenge: write a servlet that crashes tomcat (running as a windows
service) without generating any logs!

I'm just looking for any hints about what areas I whould be looking into.

Thanks.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]