You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Bryan Zimmer <ba...@baz-tech.com> on 2002/07/08 03:41:45 UTC
Problems stopping tomcat 4.0.4 on linux
Greetings,
I am running Tomcat and Apache together on a RedHat Linux box. Up until
recently they seem to have done quite well. I recently encountered a problem
that I can not trace to any configuration change that I made - I made few or
none - although the problem seems related to configuration. Just today I
installed the rpm version of Tomcat 4.0.4, upgrading from 4.0.3, first
wiping out the old tomcat installation (but saving the important config
files in a different directory). I still get the same results.
On RedHat, the startup script is invoked by issuing the command "service
tomcat4 start", and correspondingly to shut down "service tomcat4 stop".
What happens is that Tomcat seems to start up without complaint, although
its /webapps/examples directory was inaccessible. That may have been an
Apache problem configuring mod_webapp.so and the WarpConnection, or the
directory aliases (do they end with a slash or not? Is there a printed or
online guide to configuring mod_webapp and WarpConnection?).
However, when I issued the command "service tomcat4 stop", I got the
following output:
Stopping tomcat4:
Using CATALINA_BASE: /var/tomcat4
Using CATALINA_HOME: /var/tomcat4
Using CATALINA_TMPDIR: /var/tomcat4/temp
Using JAVA_HOME: /usr/java/jdk <<--- symbolic link to my
/usr/java/j2sdk1.4.0
Catalina.stop: java.net.NoRouteToHostException: No route to host
java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
at java.net.Socket.connect(Socket.java:425)
at java.net.Socket.connect(Socket.java:375)
at java.net.Socket.<init>(Socket.java:290)
at java.net.Socket.<init>(Socket.java:118)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:831)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:683)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
FAILED
Tomcat actually did stop, but I can't understand the meaning of "No route to
host". The localhost and the machines external IP addresses are both in my
routing table. I checked all the config files I could think of, but couldn't
come up with any ideas.
Can anyone help me solve this dilemma?
Also, I had to use the --nodeps switch on rpm when installing 4.0.4, because
rpm was unaware of the existence of log4j on my machine, but that's another
matter.
Thanks,
Bryan A. Zimmer
baz@baz-techNOSPAM.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Problems stopping tomcat 4.0.4 on linux
Posted by zaid haque <za...@debugisp.com>.
Hi
I hope following is one of the best document I found useful for WARP
configuration.
http://www.codesta.com/knowledge/technical/tomcat_warp_apache/page_01.jsp
Zaid.
-----Original Message-----
From: Bryan Zimmer [mailto:baz@baz-tech.com]
Sent: Monday, July 08, 2002 7:42 AM
To: Tomcat Users
Subject: Problems stopping tomcat 4.0.4 on linux
Greetings,
I am running Tomcat and Apache together on a RedHat Linux box. Up until
recently they seem to have done quite well. I recently encountered a problem
that I can not trace to any configuration change that I made - I made few or
none - although the problem seems related to configuration. Just today I
installed the rpm version of Tomcat 4.0.4, upgrading from 4.0.3, first
wiping out the old tomcat installation (but saving the important config
files in a different directory). I still get the same results.
On RedHat, the startup script is invoked by issuing the command "service
tomcat4 start", and correspondingly to shut down "service tomcat4 stop".
What happens is that Tomcat seems to start up without complaint, although
its /webapps/examples directory was inaccessible. That may have been an
Apache problem configuring mod_webapp.so and the WarpConnection, or the
directory aliases (do they end with a slash or not? Is there a printed or
online guide to configuring mod_webapp and WarpConnection?).
However, when I issued the command "service tomcat4 stop", I got the
following output:
Stopping tomcat4:
Using CATALINA_BASE: /var/tomcat4
Using CATALINA_HOME: /var/tomcat4
Using CATALINA_TMPDIR: /var/tomcat4/temp
Using JAVA_HOME: /usr/java/jdk <<--- symbolic link to my
/usr/java/j2sdk1.4.0
Catalina.stop: java.net.NoRouteToHostException: No route to host
java.net.NoRouteToHostException: No route to host
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
at java.net.Socket.connect(Socket.java:425)
at java.net.Socket.connect(Socket.java:375)
at java.net.Socket.<init>(Socket.java:290)
at java.net.Socket.<init>(Socket.java:118)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:831)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:683)
at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
FAILED
Tomcat actually did stop, but I can't understand the meaning of "No route to
host". The localhost and the machines external IP addresses are both in my
routing table. I checked all the config files I could think of, but couldn't
come up with any ideas.
Can anyone help me solve this dilemma?
Also, I had to use the --nodeps switch on rpm when installing 4.0.4, because
rpm was unaware of the existence of log4j on my machine, but that's another
matter.
Thanks,
Bryan A. Zimmer
baz@baz-techNOSPAM.com
--
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>