tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julio Serje (@canada.com)" <jse...@home.com>
Subject Re: socket exception errors on startup
Date Wed, 01 Nov 2000 02:17:23 GMT
It may be that a) you have another process that is using port 8080, or b)
you already have an instance of tomcat running that is using that port.

In case a), change in server.xml the port number Tomcat is listening to.

Julio Serje
Calian Tech.

----- Original Message -----
From: John Howay <jhoway@Radix.Net>
To: <tomcat-user@jakarta.apache.org>
Sent: Tuesday, October 31, 2000 4:13 PM
Subject: socket exception errors on startup


> My system is Red Hat Linux 6.2, Apache 1.3, JDK/JRE 1.1.8, Tomcat 3.1 and
I
> used an RPM for mod_jk--a 3.2 beta version. I'm trying to start Tomcat as
a
> standalone (using ./tomcat.sh run). I get a bunch of error messages like
> so:
>
> java.net.SocketException: Socket closed
> at java.net.PlainSocketImpl
> at java.net.Socket
> at java.net.ServerSocket.implAccept
> at java.net.ServerSocket.accept
> at org.apache.tomcat.service.SimpleTcpEndpoint
> at org.apache.tomcat.service.TcpListenerThread
> at java.lang.Thread.run
> Endpoint ServerSocket[address=0.0.0.0/0.0.0.0, port=0, localport=8080
>
> I've found similar submissions on this subject but couldn't find replies.
> Thanks for any suggestions.
> John Howay
>
>


Mime
View raw message