Tocat Server Starts, but can not access

[podsdswrk]

Background,

Tomcat-Standalone
Apache Tomcat/4.1.12
Unix Solaris 2.8

Has been running now for quite a while ... no problems.
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8085
[INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8443

Recently when shutting down the following error occurs ...

Catalina.stop: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:142)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:129)
at java.net.Socket.<init>(Socket.java:273)
at java.net.Socket.<init>(Socket.java:100)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:579)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:402)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)


... So I kill the process manually and life goes on.

I am now at the point that I cannot access the server with a browser and do not know what to look at next.

anyone every see this?

 

[sedj]

>>>> Catalina.stop: java.net.ConnectException: Connection refused
java.net.ConnectException: Connection refused

This error means that when starting or stopping the tomcat, the port (eg 8080) either is being used by something else, or there is nothing running on that port.

Ben

 

[podsds]

Well here is what I found. We run at two connectors, on at port 8085 and a secured one at port 8443. I scanned the two ports using nmap from a Linux system and found that port 8443 is closed. Now I don't know how this has happened or who has closed it. Can the port just be stuck or hung, and if so how do i clear it. I have scheduled a re-boot to occur this week-end and hope this will fix it. Of if any one has another idea ... let me know.

FYI a modification to server.xml removing the connector to 8443 has made everything okay for now.

 

[podsdswrk]

Server was rebooted and now all is fine. The port got hosed, now I should find a way to reset ports without re-booting.