RE: Unexpected tomcat 4.1.27-30 shutdown problem

2004-04-13 Thread Shapira, Yoav

Hi,

>Would an exeception in the code cause tomcat to stop?

Depends what code: it'd have to be something that percolates all the way
to the main launcher clause...

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Unexpected tomcat 4.1.27-30 shutdown problem

2004-04-12 Thread Nocera, Andrew A (Andy), ALABS
Hi,

Would an exeception in the code cause tomcat to stop?

Andy 

---tail catalina.out  

Stopping service Tomcat-Standalone
[INFO] Http11Protocol - -Stoping http11 protocol on 8099
Catalina:type=ThreadPool,name=http8099


-tail localhost_log.2004-04-12.txt
2004-04-12 16:45:00 ApplicationDispatcher[/SCME] Servlet.service() for
servlet j
sp threw exception
org.apache.jasper.JasperException
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper
.java:254)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:2
95)

2004-04-12 16:46:22 StandardHost[localhost]: Removing web application at
context path /SCME
2004-04-12 16:46:23 StandardHost[localhost]: Removing web application at
context path /examples
2004-04-12 16:46:23 StandardHost[localhost]: Removing web application at
context path /webdav
2004-04-12 16:46:23 StandardHost[localhost]: Removing web application at
context path /tomcat-docs
2004-04-12 16:46:23 StandardHost[localhost]: Removing web application at
context path /manager

---
tail localhost_examples_log.2004-04-12.txt
2004-04-12 16:46:23 SessionListener: contextDestroyed()
2004-04-12 16:46:23 ContextListener: contextDestroyed()
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Monday, April 12, 2004 8:44 AM
To: Tomcat Users List
Subject: RE: Unexpected tomcat 4.1.27-30 shutdown problem



Hi,
>I am running tomcat 4.1.27/29/30 on a Solaris 5.7 or 5.8 and it
shutsdown
>for no
>apparent reason.   Sometimes it can go for hours without a problem,
>othetimes it stops much
>sooner.  There is no obvious error, just a shutdown.  The same code
built
>on another Solaris box and/or HPUX runs without a problem.  Any ideas
how I
>can debug this?

When it shuts down, are there files named 'core' and 'hs_err_pid'
(where  is the process ID of the server) in the working directory?
If so, what do those files contain?

The advice at this point is generic: make sure the box has the latest
Sun OS patches required for your JDK (these patches are available on the
JDK download page near the bottom), and make sure the user account
running the server has sufficient file descriptors and threads (the
ulimit settings).

Yoav Shapira



This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged.  This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender.  Thank you.


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



RE: Unexpected tomcat 4.1.27-30 shutdown problem

2004-04-12 Thread Shapira, Yoav

Hi,
>I am running tomcat 4.1.27/29/30 on a Solaris 5.7 or 5.8 and it
shutsdown
>for no
>apparent reason.   Sometimes it can go for hours without a problem,
>othetimes it stops much
>sooner.  There is no obvious error, just a shutdown.  The same code
built
>on another Solaris box and/or HPUX runs without a problem.  Any ideas
how I
>can debug this?

When it shuts down, are there files named 'core' and 'hs_err_pid'
(where  is the process ID of the server) in the working directory?
If so, what do those files contain?

The advice at this point is generic: make sure the box has the latest
Sun OS patches required for your JDK (these patches are available on the
JDK download page near the bottom), and make sure the user account
running the server has sufficient file descriptors and threads (the
ulimit settings).

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Unexpected tomcat 4.1.27-30 shutdown problem

2004-04-09 Thread Nocera, Andrew A (Andy), ALABS
Hi,

I am running tomcat 4.1.27/29/30 on a Solaris 5.7 or 5.8 and it shutsdown for no 
apparent reason.   Sometimes it can go for hours without a problem, othetimes it stops 
much
sooner.  There is no obvious error, just a shutdown.  The same code built on another 
Solaris box and/or HPUX runs without a problem.  Any ideas how I can debug this?


Thanks,
Andy

Starting service Tomcat-Standalone
Apache Tomcat/4.1.29
[INFO] PropertyMessageResources - -Initializing, config='org.apache.struts.util.
LocalStrings', returnNull=true
[INFO] PropertyMessageResources - -Initializing, config='org.apache.struts.actio
n.ActionResources', returnNull=true
[INFO] PropertyMessageResources - -Initializing, config='org.apache.webapp.admin
.ApplicationResources', returnNull=true
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080
[INFO] ChannelSocket - -JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009
[INFO] JkMain - -Jk running ID=0 time=1/51  config=/export/home/wscmeadm/jakarta
-tomcat-4.1.29/conf/jk2.properties
Stopping service Tomcat-Standalone
[INFO] Http11Protocol - -Stoping http11 protocol on 8080 Catalina:type=ThreadPoo
l,name=http8080

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]