I just upgraded from 4.1.30 to 5.0.28 on two windows machines: one XP
and one W2K. Both of them are having the same problem:
When I stop the installed Tomcat service, the destroy() method on my
servlets does not appear to get called. I do not get my logging
information from my destroy
, fixed for 5.0.16 or 5.0.19,
and now apparently has re-appeared.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Paul Christmann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 16, 2004 3:53 PM
To: [EMAIL PROTECTED]
Subject: 5.0.28 Service Shutdown problem on Windows
I
To: [EMAIL PROTECTED]
Subject: 5.0.28 Service Shutdown problem on Windows
I just upgraded from 4.1.30 to 5.0.28 on two windows machines: one XP
and one W2K. Both of them are having the same problem:
When I stop the installed Tomcat service, the destroy() method on my
servlets does not appear to get
Hi!
My system: Tomcat 5.0.28 on Fedora Core 2.
Server Startup is normal. However, during shutdown looks like there is a
problem in shutting Coyote down...It takes a bit more than 3 minutes till it
throws exception and dies. Here is the log:
Hi!
My system: Tomcat 5.0.28 on Fedora Core 2.
Server Startup is normal. However, during shutdown looks like there is a
problem in shutting Coyote down...It takes a bit more than 3 minutes till it
throws exception and dies. Here is the log:
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
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
-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
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
Not that I know of. I've never seen it on Red Hat, though, 7.x or 9.
John
On Mon, 16 Jun 2003 10:08:49 +0800, unplug [EMAIL PROTECTED]
wrote:
John,
I am using Redhat7.3. It still has that error. Does it any affect
for the applications if this error exists?
unplug
John Turner wrote:
AFAIK,
John,
I am using Redhat7.3. It still has that error. Does it any affect
for the applications if this error exists?
unplug
John Turner wrote:
AFAIK, it is a timing issue, only on Solaris. The port binding is released
before the shutdown is completely finished, which throws the error.
AFAIK, it is a timing issue, only on Solaris. The port binding is released
before the shutdown is completely finished, which throws the error. I'm
pretty certain it can be ignored until it is fixed.
John
On Thu, 12 Jun 2003 07:21:08 -0400, Tim Funk [EMAIL PROTECTED] wrote:
Looks like this
Looks like this bug report.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20663
Does anyone know what this is?
-Tim
unplug wrote:
Hi all,
I am using tomcat4.1.24 but there is an exception during shutdown.
When I issue catalina.sh stop, below exception shown in the
catalina.out.
Hi all,
I am using tomcat4.1.24 but there is an exception during shutdown.
When I issue catalina.sh stop, below exception shown in the
catalina.out. It seems a socket connection problem. I am using the
default server.xml without any modification. Does anyone know what
wrong with it? How
I have a problem with tomcat 3.3.1a installed in a Solaris environment.
When I use the shutdown.sh-script the java process is left alive. This
happens if I have two instances of the same webapplication installed in
the webapps-directory(with different names). If I remove one of the
hi all,
sorry to repost the same question but nobuddy responded
that's why this repeat.
anybody knows what the foll. errror msg in tomcat means?
this msg was logged in the error.log file in the bin folder of tomcat.
i'm using tomcat 3.3.
JNI panic: native code passed a wrong class to a static
i'm using jdk1.3.
any incompatibility with tomcat 3.3.
thanx for y'r response raj.
nitin
- Original Message -
From: Raj Saini [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, October 14, 2002 1:57 PM
Subject: Re: tomcat auto shutdown problem
Please check
:[EMAIL PROTECTED]]
Sent: Tuesday, September 10, 2002 7:32 PM
To: [EMAIL PROTECTED]
Subject: Shutdown problem
Perhaps this was discussed before... I can't find a suitable solution
to my
problem on the archives...
When I stop tomcat using the shutdown.bat (shutdown.sh) on Windows
2000,
the
java process
-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 9:01 AM
To: Tomcat Users List
Subject: RE: Shutdown problem
Hi,
This was discussed many times ;)
You probably have non-daemon threads still running. The JVM will keep
running as long as non-daemon threads haven't
Perhaps this was discussed before
I cant find a suitable solution to my
problem on the archives
When I stop tomcat using the shutdown.bat (shutdown.sh) on Windows 2000, the
java process in which tomcat runs is not terminated. While servlets are
active, they no longer respond to requests
I am using Tomcat 4.0.4 with JDK 1.3 on Debian Linux 2.2.6.
Tomcat starts OK with startup.sh and I can see the home page.
On shutdown with shutdown.sh, there are no error messages on the xterm.
Subsequent startup does not succeed and I cannot see the home page.
There is no conflict with the
I checked for temp files in $CATALINA_HOME/work and $CATALINA_HOME/temp dirs,
but there are none. I also tried killing the tomcat processes but they restart.
I am stuck... any help is very welcome.
Thanks,
Anand
I am using Tomcat 4.0.4 with JDK 1.3 on Debian Linux 2.2.6.
Tomcat starts OK
I am using Tomcat 4.0.4 with JDK 1.3 on Debian Linux 2.2.6.
Tomcat starts OK with startup.sh.
On shutdown with shutdown.sh, there are no error messages on the xterm.
Subsequent startup does not succeed.
I have searched the newsgroups and this mailing list but I cannot find a
solution to this
Hi
I have the following setup
1) Apache 1.3
2) Tomcat 3.2
3) Java SDK 1.3.1_01
Running on a Solaris box with SunOS Release 5.6. I have made sure that i
have all the patches for Java are present on the Sun Box. But my Tomcat
is shutdown frequently, and i have notices that it is creating a log
hi,
I am installing tomcat3.2 rpm on Sun java 1.3.1 in linux, well it installed
properly with a startup script in /etc/rc.d/init.d, but the shutdown part is
not working. after I give the command tomcat stop and run netstat I see two
java programs running still on 8080 and 8007. The script says
i would like to stop tomcat4.0 no matter what the states of the servlets
are. here is my situation.
WHILE the LoginServlet is running, client stops the client program that
calls the servlet. i then used 'catalina.sh stop' command to stop tomcat.
the log then showed
-To: Tomcat Users List [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: catalina shutdown problem - waiting for instance to be
deallocate d
i would like to stop tomcat4.0 no matter what the states of the servlets
are. here is my situation.
WHILE the LoginServlet is running
List
Subject: Re: catalina shutdown problem - waiting for instance to be
deallocate d
There was a bug in the 4.0 release that made Tomcat think a
servlet was
still in use when it wasn't. I thought this was fixed in
4.0.1 -- which
are you using?
Craig
--
To unsubscribe: mailto
On Fri, 2 Nov 2001, Tsai, Eddie wrote:
Date: Fri, 2 Nov 2001 15:55:27 -0600
From: Tsai, Eddie [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Subject: RE: catalina shutdown problem - waiting for instance to be
deallo cate d
tomcat.sh you can add a line to kill all tomcat process to insure that no
more tomcat process are running.
-Original Message-
From: Jurrius, Mark [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 20, 2001 1:44 AM
To: [EMAIL PROTECTED]
Subject: RE: TOMCAT SHUTDOWN PROBLEM
We have the same
When i try to shutdown Tomcat, it throws me the following exception:
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:312)
at
this with netstat (Unix or Windows) in combination with
ps/TaskManager.
Randy
-Original Message-
From: Matas Salvador [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 19, 2001 2:19 PM
To: [EMAIL PROTECTED]
Subject: TOMCAT SHUTDOWN PROBLEM
Importance: High
When i try to shutdown Tomcat
19, 2001 2:58
PM
Subject: RE: TOMCAT SHUTDOWN
PROBLEM
Possibilities I see:1. You have disabled AJP12 in
your server.xml file (needed toshutdown)2. Tomcat is only
getting halfway shutdown - it stops acceptingAJP12 connections but still
keeps the HTTP connection open. I've
I have tomcat shutdown problem on HP-UX. At first I had to kill it. Then
I found that it would be shutdown after running "tomcat.sh stop" three
times.
I have not spent time to figure out why. Anybody has some ideas about it?
Should I change the tomcat.sh scripts? Thanks for
To: '[EMAIL PROTECTED]'
Subject:RE: TOMCAT SHUTDOWN PROBLEM
I have tomcat shutdown problem on HP-UX. At first I had to kill it. Then
I found that it would be shutdown after running "tomcat.sh stop" three
times.
I have not spent time to figure out why. Anybody has some i
Hi !
We are running tomcat 3.2 and IBMJava2 SDK 1.3 on an Intel Red Hat 6.2
machine with Apache 1.3.12 and mod_jserv.
When shutdown.sh is called, it is very rare that the contexts are
removed and java processes are still running for some minutes. Sometimes
they don't disappear at all and have
Hello!
On Wed, 07 Mar 2001 16:38:40 +0100, Peter Hrastnik wrote:
We are running tomcat 3.2 and IBMJava2 SDK 1.3 on an Intel Red Hat 6.2
machine with Apache 1.3.12 and mod_jserv.
When shutdown.sh is called, it is very rare that the contexts are
removed and java processes are still running for
I had also seen this - but after moving to rh7, it seemed to
vanish? not sure why though...
Tagunov Anthony wrote:
Hello!
On Wed, 07 Mar 2001 16:38:40 +0100, Peter Hrastnik wrote:
We are running tomcat 3.2 and IBMJava2 SDK 1.3 on an Intel Red Hat 6.2
machine with Apache 1.3.12 and
TECTED]]
Sent: Friday, February 23, 2001 3:51 PM
To: [EMAIL PROTECTED]
Subject:Shutdown problem
Hi Folks!!
I am using Tomcat 3.2 on Solaris.
My problem is I can not shutdown the server and bring it up with the
tomcat.sh stop/start command. I get the exception "Fatal:
java.net.Bi
Even i
get problems with shutting down tomcat both on Linux and in Windows NT machine,
you can just kill the damn window. :-)
-Original Message-From: Tomas Marek
[mailto:[EMAIL PROTECTED]]Sent: Sunday, November 26, 2000 12:28
PMTo: TomcatSubject: Shutdown
problemGuys, I
. :-)
-Original
Message-
From: Tomas Marek [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26,
2000 12:28 PM
To: Tomcat
Subject: Shutdown problem
Guys,
I start Tomcat 3.1 perfectly and when I run Shutdown.bat script, the
Java window is still on with the following content:
Out
NT machine, you can just
kill the damn window. :-)
-Original Message- From: Tomas Marek [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 26, 2000
12:28 PM To:
Tomcat Subject:
Shutdown problem Guys, I start Tomcat
3.1 perfectly and when I
42 matches
Mail list logo
