tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jm...@adobe.com
Subject Re: A problem with Tomcat and port 8080
Date Sun, 16 Feb 2003 23:41:49 GMT
Try

netstat -a | grep 8080 and see if you see something like

*.8080 .... LISTEN

Like Jake mentioned, its possible that the instance might still be 
running... also check for permissions and see if there are any file 
permissions problem.

Finally issue a telnet request to the port and see if it responds

# telnet localhost 8080
if you get a response, then your server is still at work.. finally 
tomcat might not be the only guy who's running on your box that is 
using that port.. other services or rmi services you've configured in 
the past for example might be using that port.

The alternate way (if you can't figure out the problem) is to edit the 
startup port that tomcat uses change it to 28080 or some high port 
that you know is not being used.

Hope that helps

Jan-Michael

----- Original Message -----
From: "Michael Harrison" <michael@domanistudios.com>
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 wasn't running either. Then I ran bin/startup.sh. But 
> I got
> nothing at localhost:8080, and logs/catalina.out recorded this error:
> 
> Catalina.start: LifecycleException:  null.open:  
> java.net.BindException:Address already in use:8080
> LifecycleException:  null.open:  java.net.BindException: Address 
> already in
> use:8080
>        at
> org.apache.catalina.connector.http.HttpConnector.initialize
(HttpConnector.ja
> va:1130)
> 
> Thanks for the suggestion, Jake, but there's something else at 
> work here.
> Maybe I should just reinstall Apache and Tomcat, again.
> 
> Michael
> 
> ----- Original Message -----
> From: "Jake Robb" <jakerobb@mac.com>
> To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
> Sent: Sunday, 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 send.  The kernel won't let the 
> process> ignore or catch the signal.
> >
> > What I would do, though, is remove your old Tomcat installation 
> entirely,> and move the new one into the old one's location.  It 
> can't run if it's
> not
> > there.  :-)
> >
> > -Jake
> >
> >
> > 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 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
> 8080.
> > >
> > > When I startup Tomcat, it writes an error to logs/catalina.out 
> about a
> > > BindException: address already in use:8080. To try to shut off 
> whatevermight
> > > be listening on 8080, I've made sure to kill the 'java' 
> process for
> Tomcat and
> > > Apache (which starts automatically when rebooting). But I 
> still get the
> same
> > > error.
> > >
> > > Another strange thing: despite the BindException, the 'java' 
> processkeeps
> > > running. Executing shutdown.sh produces the four "Using..." 
> lines of
> output
> > > and then hangs--I have to use Ctrl-C to get a prompt back, and 
the
> 'java'
> > > process continues to run.
> > >
> > > Also: a bit of history. I had Tomcat working OK on 8080 a few 
> days ago.
> Then I
> > > began working to set up the connector: I complied a mod_jk and 
> set up
> > > httpd.conf with the proper directives. Something I did must have
> offended
> > > Tomcat, because it stopped responding on 8080. To get a fresh 
> start, I
> > > downloaded a new copy of Tomcat this morning and installed it 
> in a
> separate
> > > directory under /usr/local. It's this new copy that has been 
> returningthe
> > > BindException.
> > >
> > > The sysadmin assures me that port 8080 is not being blocked on 
the
> machine,
> > > either.
> > >
> > > Thanks,
> > >
> > > Michael
> > >
> > >
> >
> >
> > -----------------------------------------------------------------
> ----
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-
help@jakarta.apache.org
> 
> 
> -------------------------------------------------------------------
> --
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message