H-
Yes that was it.
Once that process was killed, tomcat started right up.
Strange.
Thanks to all for assisting with this.
Your clues and advice are much appreciated.
Thanks.
-Sterling
Randy Layman wrote:
> The problem seems to be that you started Tomcat, tried to stop
> Tomcat, and tried to start Tomcat again. The output of ps -ef you posted
> earlier shows that Tomcat is still running. If I remember correctly the
> people here who were using Kaffe with Tomcat were having networking problems
> (it wasn't shutting down correctly was one of the complaints, IIRC). It
> seems that you have been bitten by the same problem. Try killing the Kaffe
> process (or restarting the machine if you don't want to mess with killing
> processes) and try starting Tomcat again. Assuming that Tomcat is not set
> to automatically start on boot, you should be able to start Tomcat after a
> reboot.
>
> To recap, the problem is with how Kaffe implements some of the
> network APIs so it causes it to not release ports and to not shutdown when
> the shutdown script is run.
>
> Randy
>
> -----Original Message-----
> From: Sterling [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 03, 2001 2:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat Standalone worked, now doesn't.
>
> H-
>
> This is a confusing situation.
>
> Because...
> I installed tomcat in the /usr/local/ directory, Java (JDK1.3) in the same
> directory. Grabbed an older version of stdc++ library.
> After these three things were put on everything worked fine. Servlets, jsp
> pages
> everything through the 8080 port.
>
> Then I shut it down because of the aforementioned conflicts (which cleared
> up upon
> shutting down) and now it won't work.
>
> I'm thinking of just deleting the jakarta directory and untaring the file
> again. I
> spoke to another who is using the machine and they say that Kaffe has been
> on the
> system since day one and tomcat was working with that system than.
>
> Here's what the java -version pulled up.
> Kaffe Virtual Machine
> Copyright (c) 1996-1999
> Transvirtual Technologies, Inc. All rights reserved
> Engine: Just-in-time v3 Version: 1.0.5 Java Version: 1.1
>
> Why would it work without any modifications on the first try before and not
> work
> now? I only modified apache conf files.
> I'm at a total loss. Nothing has changed except the apache conf files and
> they were
> just set to use ssi, and activate cgi-bin.
>
> Aak!
> -Sterling
>
> Travis Low wrote:
>
> > Ack! You are not using Sun's JDK, perhaps that is the problem? Kaffe
> > always gives me a headache. Each time I install a machine (too
> > often), I delete all the java-related binaries in /usr/bin. Try "java
> > -version" and see what you're really running.
> >
> > T
> >
> > Sterling wrote:
> > >
> > > H-
> > >
> > > Thanks for the reply. That was my thoughts but I didn't know how to
> determine
> > > what was listening to what.
> > > I did a ps -ef and this is an entry that caught my attention.
> > >
> > > root 13970 1 0 Jan02 ? 00:00:11 /usr/lib/kaffe/bin/Kaffe
> > > -Dtomcat.home ./bin/.. org.apache.tomcat.startup.Tomcat
> > >
> > > Could this be preventing Tomcat from running?
> > > Looks very suspicious but don't want to kill it unless I'm sure.
> Although it's
> > > very convincing I'd rather be safe than sorry at this point.
> > >
> > > Thoughts, Comments, Anecdotes ?
> > > -Sterling
> > >
> > > Ritwick Dhar wrote:
> > >
> > > > In my experience, this problem has one source - your box is running
> some
> > > > server that's listening to the same port that Tomcat is trying to
> listen to.
> > > > Since you say that you have a problem running Apache and tomcat
> > > > simultaneously, it sounds like Tomcat's web server has been configured
> to
> > > > listen to port 80, which Apache listens to by default. The best thing
> to do
> > > > would be:
> > > >
> > > > 1. Do a 'ps -ef' (or the equivalent on your OS) and check that Apache
> has
> > > > *really* stopped, and that no other servers which *could* listen to
> the same
> > > > ports (80, 8080) are running.
> > > >
> > > > 2. Try starting Tomcat again. If this still doesn't work, try changing
> the
> > > > port that Tomcat listens to. You can try something like 8888. Any
> arbitrary
> > > > large number should do. (If you want to use a port below 1000 (?), you
> must
> > > > be root).
> > > >
> > > > Rit
> > > >
> > > > -----Original Message-----
> > > > From: Sterling [mailto:[EMAIL PROTECTED]]
> > > > Sent: Wednesday, January 03, 2001 11:39 AM
> > > > To: Tomcat
> > > > Subject: Tomcat Standalone worked, now doesn't.
> > > >
> > > > H-
> > > >
> > > > I'm trying to get Tomcat working as a stand alone on my server. Again.
> > > >
> > > > I have unzipped/tared the 3.2 binary into the usr/local directory.
> > > > Tomcat was working before but for some reason it appeared to be
> > > > interferring with Apache and would grab the pages first (timeout) than
> > > > apache would display the page. It also prevented cgi scripts from
> being
> > > > run.
> > > >
> > > > This was confirmed when I ./bin/shutdown.sh tomcat and all those
> > > > problems went away. My apache server worked fine.
> > > > I'm not looking to merge the two.
> > > >
> > > > But now that I try to restart Tomcat it doesn't work.
> > > > I have set all the env variables.
> > > > TOMCAT_HOME=/usr/local/jakarta-tomcat-3.2.1; export TOMCAT_HOME
> > > > JAVA_HOME=/usr/local/jdk1.3; export JAVA_HOME
> > > > CLASSPATH=/usr/local/jdk1.3/lib/tools.jar ; export CLASSPATH
> > > >
> > > > Thinking that apache might be interferring with tomcat's start up (it
> > > > complained of an address already in use) I stopped apache
> > > > (/etc/init.d/apache stop) than ran ./bin/startup.sh. This is what it
> > > > did.
> > > > Using classpath:
> > > >
> /usr/local/jakarta-tomcat-3.2.1/lib/ant.jar:/usr/local/jakarta-tomcat-3.2.1/
> > > >
> lib/jasper.jar:/usr/local/jakarta-tomcat-3.2.1/lib/jaxp.jar:/usr/local/jakar
> > > >
> ta-tomcat-3.2.1/lib/parser.jar:/usr/local/jakarta-tomcat-3.2.1/lib/servlet.j
> > > >
> ar:/usr/local/jakarta-tomcat-3.2.1/lib/test:/usr/local/jakarta-tomcat-3.2.1/
> > > >
> lib/webserver.jar:/usr/local/jdk1.3/lib/tools.jar:/usr/local/jdk1.3/lib/tool
> > > > s.jar
> > > >
> > > > XXXXXX:/usr/local/jakarta-tomcat-3.2.1# 2001-01-03 12:23:27 -
> > > > ContextManager: Adding context Ctx( /examples )
> > > > 2001-01-03 12:23:27 - ContextManager: Adding context Ctx( /admin )
> > > > Starting tomcat. Check logs/tomcat.log for error messages
> > > > 2001-01-03 12:23:27 - ContextManager: Adding context Ctx( )
> > > > 2001-01-03 12:23:27 - ContextManager: Adding context Ctx( /test )
> > > > FATAL:java.net.BindException: Address already in use
> > > > java.net.BindException: Address already in use
> > > > at java.net.PlainSocketImpl.socketBind(Native Method)
> > > > at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:397)
> > > >
> > > > Those FATAL.java.net errors I think are the main problem but I don't
> > > > know what could be causing them.
> > > > BTW - there is no tomcat.log file. There is a servlet and jasper.log
> > > > file. I have pasted them below. As you can see not much there.
> > > > Anyone have any thoughts on what it could be and how to fit it?
> > > > Any info or assistance is much appreciated.
> > > > Thanks.
> > > > -Sterling
> > > >
> > > > PS(I'm running Debian 2.2rev2, JDK1.3, Tomcat3.2.1, and I downloaded
> the
> > > > old Java library which was preventing it from running the first time.)
> > > > xxxxxxx:/usr/local/jakarta-tomcat-3.2.1/logs# less jasper.log
> > > > 2001-01-03 12:23:28 - Scratch dir for the JSP engine is:
> > > > /usr/local/jakarta-tomcat-3.2.1/work/localhost_8080%2Fexamples
> > > > 2001-01-03 12:23:28 - IMPORTANT: Do not modify the generated servlets
> > > > xxxxxxx:/usr/local/jakarta-tomcat-3.2.1/logs# less servlet.log
> > > > 2001-01-03 12:23:28 - path="/examples" :jsp: init
> > > > 2001-01-03 12:23:28 - path="/admin" :jsp: init
> > > > 2001-01-03 12:23:28 - path="" :jsp: init
> > > > 2001-01-03 12:23:29 - path="/test" :jsp: init
> > > > This was created right after I ran the ./bin/startup.sh script.
> > > > Well if you have any thoughts I'd love to hear them. Thanks.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> >
> > -- Travis Low
> > <mailto:[EMAIL PROTECTED]>
> > <http://dawnstar.org/travis>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
