You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Peter Courcoux <pe...@courcouxhall.co.uk> on 2002/10/14 22:17:06 UTC
catalina shutdown
Hi all,
When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it
stopping. However, the jvm processes still appear in the process list
and attempting to start catalina again results in a
java.net.bindException Address already in use :8080.
I cannot see anything obvious in turbine.log either.
I am using redhat 7.2, sun jdk1.3.1_02, tdk as above. I have to kill the
jvm to be able to start catalina again. Does anyone have any clues as to
why this may be happening? I think the shutdown is leaving postges db
connections from the turbine webapp open and idle. Could this have
something to do with it?
Any thoughts or pointers would be very welcome.
Thanks
Peter Courcoux
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: catalina shutdown
Posted by Rodney Schneider <ro...@actf.com.au>.
On Tue, 15 Oct 2002 06:17, you wrote:
> Hi all,
>
> When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it
> stopping. However, the jvm processes still appear in the process list
> and attempting to start catalina again results in a
> java.net.bindException Address already in use :8080.
If there is a user (non-daemon) thread still running, it will keep the JVM
alive. Try this:
cd $TDK_HOME/bin
./catalina.sh run
Then press <Ctrl>-<\> to get a full JVM thread dump. That will help you
analyse which threads are running in that JVM. I think you can also do this
by sending a SIGQUIT signal to the JVM process if you use the catalina
startup.sh and shutdown.sh scripts. See "man kill".
Regards,
-- Rodney
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: catalina shutdown
Posted by CP Lim <cp...@redsheriff.com>.
Hi Peter,
Just adding my voice to your findings, and yes I noticed it too on my
system (Mandrake 8.2, Sun JDK 1.4.0). I would also be interested in
finding out why this is happening.
CP
Peter Courcoux wrote:
> Hi all,
>
> When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it
> stopping. However, the jvm processes still appear in the process list
> and attempting to start catalina again results in a
> java.net.bindException Address already in use :8080.
>
> I cannot see anything obvious in turbine.log either.
>
> I am using redhat 7.2, sun jdk1.3.1_02, tdk as above. I have to kill the
> jvm to be able to start catalina again. Does anyone have any clues as to
> why this may be happening? I think the shutdown is leaving postges db
> connections from the turbine webapp open and idle. Could this have
> something to do with it?
>
> Any thoughts or pointers would be very welcome.
>
> Thanks
>
> Peter Courcoux
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: catalina shutdown
Posted by Peter Courcoux <pe...@courcoux.biz>.
Thanks to Rodney and Rogelio,
Examination of a thread dump did indeed show user threads hanging about
from the xml-rpc service. Commenting out the xml-rpc service settings in
TR.props solved the problem as I wasn't using the service.
Presumably this must be a problem if the xml-rpc service is required for
the webapp? Should there be an issue on scarab?
Regards,
Peter
On Tue, 2002-10-15 at 01:21, Rodney Schneider wrote:
> On Tue, 15 Oct 2002 06:17, you wrote:
>
> > Hi all,
> >
> > When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it
> > stopping. However, the jvm processes still appear in the process list
> > and attempting to start catalina again results in a
> > java.net.bindException Address already in use :8080.
>
> If there is a user (non-daemon) thread still running, it will keep the JVM
> alive. Try this:
>
> cd $TDK_HOME/bin
> ./catalina.sh run
>
> Then press <Ctrl>-<\> to get a full JVM thread dump. That will help you
> analyse which threads are running in that JVM. I think you can also do this
> by sending a SIGQUIT signal to the JVM process if you use the catalina
> startup.sh and shutdown.sh scripts. See "man kill".
>
> Regards,
>
> -- Rodney
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: catalina shutdown
Posted by Will Glass-Husain <wg...@forio.com>.
Hi,
Had the same problem. Commenting out this line in Fulcrum.properties worked
for me. (Thanks Peter). I'll note that this may be in both
TurbineResources.properties and Fulcrum properties.
services.XmlRpcService.classname=org.apache.fulcrum.xmlrpc.TurbineXmlRpcServ
ice
Best, WILL
-----Original Message-----
From: Peter Courcoux [mailto:peter@courcouxhall.co.uk]
Sent: Monday, October 14, 2002 1:17 PM
To: Turbine Users ListTurbineUsersList
Subject: catalina shutdown
Hi all,
When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it
stopping. However, the jvm processes still appear in the process list
and attempting to start catalina again results in a
java.net.bindException Address already in use :8080.
I cannot see anything obvious in turbine.log either.
I am using redhat 7.2, sun jdk1.3.1_02, tdk as above. I have to kill the
jvm to be able to start catalina again. Does anyone have any clues as to
why this may be happening? I think the shutdown is leaving postges db
connections from the turbine webapp open and idle. Could this have
something to do with it?
Any thoughts or pointers would be very welcome.
Thanks
Peter Courcoux
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>