Looks like something is calling tomcat PAUSE command from the tomcat
command port. It may not be related to Exception you get prior but more
related to some external process giving instructions to pause on tomcat
administrator interface. Tomcat in itself catches all Exception that
occur during jsp execution and return error page, it will not pause as a
result of an exception. Now, maybe the "application someone wrote" is
doing nasty stuff with tomcat administration port, but it's impossible
for us to tell.
Tony Chamberlain a écrit :
I was running a jsp application here via TomCat that someone wrote.
I got no response, and when I looked in catalina.out I saw
Couldn't open execbin/dMAX-Dog.config/home/span/execbin/dMAX-Dog.config (No
such file or directory)
Couldn't open dmagexec/dMAX-Dog.config/home/span/dmagexec/dMAX-Dog.config(No
such file or directory)
Jan 30, 2008 11:04:26 AM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-80
actually the file just starts from /home (the print statement is wrong).
Problem is as you can see this causes TomCat to pause (in actuality
DIE). Java no longer is running, and you can' access.
Now granted the error occured because the file was not there. I put a copy
for the file it was looking for there and our stuff worked. BUT should a
File Not Found error cause Tomcat to crash? Shouldn't it print out some
sort of exception or something, but keep going?
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
