Something is running on port 8080, it looks like the old tomcat is
running. You could try and kill all java processes in your machine to be
sure then start up your new copy.
Michael Harrison wrote:
I'm running (or trying to) Tomcat 4.0.6 on RedHat 8.0 for PC. I installed Tomcat from a binary (ie
I'm running (or trying to) Tomcat 4.0.6 on RedHat 8.0 for PC. I installed Tomcat from
a binary (ie. I just unpacked it and moved it into /usr/local. I ultimately hope to
run it connected to Apache (2.0.44) through an ajp13 connector, but for now I just
want the server to run by itself on port 80
I'm running (or trying to) Tomcat 4.0.6 on RedHat 8.0 for PC. I installed Tomcat from
a binary (ie. I just unpacked it and moved it into /usr/local. I ultimately hope to
run it connected to Apache (2.0.44) through an ajp13 connector, but for now I just
want the server to run by itself on port 80
Date: Sunday, February 16, 2003 1:52 pm
Subject: Re: A problem with Tomcat and port 8080
> I deleted my old Tomcat install, and I moved the new installation
> into the
> old one's place. I made sure there were no 'java' processes
> running, and
> that Apache w
ay, February 16, 2003 4:33 PM
Subject: Re: A problem with Tomcat and port 8080
> To me, the obvious answer is that your old version of Tomcat is still
> running.
>
> To kill a process that won't die, use `kill -9 [PID]`. -9 is the
> "strongest" kill signal you can se
To me, the obvious answer is that your old version of Tomcat is still
running.
To kill a process that won't die, use `kill -9 [PID]`. -9 is the
"strongest" kill signal you can send. The kernel won't let the process
ignore or catch the signal.
What I would do, though, is remove your old Tomcat i
I'm running (or trying to) Tomcat 4.0.6 on RedHat 8.0 for PC. I installed Tomcat from
a binary (ie. I just unpacked it and moved it into /usr/local. I ultimately hope to
run it connected to Apache (2.0.44) through an ajp13 connector, but for now I just
want the server to run by itself on port 80
