tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrice Seyed" <apse...@bu.edu>
Subject tomcat shutdown.sh doesn't kill tomcat processes
Date Thu, 25 Sep 2003 17:42:47 GMT
So the symptom is /usr/local/tomcat/bin/shutdown.sh does not stop
tomcat.
By the way tomcat is running jk2 connector on port 8080 to apache on
port 80

Even after i stop tomcat, I will see in netstat -nap | grep 8080 that
the
socket is still open, and ps -elf | grep tomcat that the process for
tomcat
are still running.
Any ideas or seen this?


When I try to stop it again of course it complains, because it thinks
its stopped;
# service tomcat stop
Stopping Tomcat
Using CATALINA_BASE:   /usr/local/tomcat
Using CATALINA_HOME:   /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JAVA_HOME:       /usr/local/java
Catalina.stop: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:426)
        at java.net.Socket.connect(Socket.java:376)
        at java.net.Socket.<init>(Socket.java:291)
        at java.net.Socket.<init>(Socket.java:119)
        at org.apache.catalina.startup.Catalina.stop(Catalina.java:581)
        at
org.apache.catalina.startup.Catalina.execute(Catalina.java:402)
        at
org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39
)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)


the corresponding out in  catalina.out is:
Catalina.start: LifecycleException:  Protocol handler initialization
failed:
java.net.BindException: Address already in use:8080
LifecycleException:  Protocol handler initialization failed:
java.net.BindException: Address already in use:8080
        at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.jav
a:11
19)
        at
org.apache.catalina.core.StandardService.initialize(StandardService.java
:579
)
        at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2
246)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:511)
        at
org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at
org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39
)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.stop: LifecycleException:  This server has not yet been started


 
 
Regards,
 
Patrice Seyed, System Administrator
RHCE, SCSA
Genetics Program, BU School of Medicine
 
 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message