I'm afraid I got this wrong again. I checked my process table again and indeed Tomcat had not started at all, and upon trying to stop, I got the exact message you described, "Connection refused".
What worked for you in this circumstance? I don't think I am doing anything different as far as configuration goes: has Tomcat4 changed in version 4.0.4? Mainly what I have done, since tomcat doesn't even start standalone, is change all the instances of "localhost" in server.xml to my server's external dns name, the name it formerly worked under when I was using 4.0.3. Since it is a test environment, there is no "www" alias or anything. Of course, I tweaked tomcat4.conf to show where my java was located, and uncommented the parts of catalina.policy that had to do with granting permissions to /webapps/examples. I am still clueless now that the problem has changed: tomcat4 won't even start standalone. Please tell me what worked for you before, I am obviously missing something, configuration-wise. Thanks, Bryan A. Zimmer [EMAIL PROTECTED] ----- Original Message ----- From: "Bryan Zimmer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Sunday, July 07, 2002 9:22 PM Subject: Re: FW: Problems stopping tomcat 4.0.4 on linux > According to my process table "ps -ef f" Tomcat4 and its numerous > sub-threads had indeed started. I haven't tweaked the config files so > I'm not yet sure if it's responding at all as a standalone server. > > Good guess, though. > > > On Sunday 07 July 2002 09:01 pm, Daniel Farinha wrote: > > That reminds me of the error I get every time I try to shutdown > > Tomcat when it is not actually running, only I get a > > "java.net.ConnectException: Connection refused". This happens often > > during my messing up with the configuration files, since the startup > > script never outputs any errors, including the fact that Tomcat might > > not have started at all (you really have to look at logs/catalina.out > > if you're not sure). When I realise something's gone wrong and try > > stopping Tomcat (without realising it wasn't running at all) then end > > up getting the Exception, along with the thread stack. > > > > Perhaps the NoRouteToHostException is also related to Tomcat not > > having initialised properly, since you do have that problem in > > /webapps/examples? > > > > Dan > > > > > -----Original Message----- > > > From: Bryan Zimmer [mailto:[EMAIL PROTECTED]] > > > Sent: 08 July 2002 02:42 > > > 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(NativeMethodAccess > > > orImpl.java:39 > > > ) > > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > > > odAccessorImpl > > > .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 > > > [EMAIL PROTECTED] > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:tomcat-user-> [EMAIL PROTECTED]> > > > For > > > additional commands, > > > e-mail: <mailto:[EMAIL PROTECTED]> > > -- > Bryan A. Zimmer > [EMAIL PROTECTED] > > Populus vult decipi. > [The people like to be deceived.] > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
