1 Reply Latest reply on Aug 21, 2003 8:06 PM by Jon Barnett

    Exception on shutdown?

    Jan Nielsen Newbie

      I use the shutdown.sh script to shut down my JBoss 3.0.8 server but often, I'm presented with the exception below. Does anyone have a clue what this means? The server shuts down ok and there are no exceptions in my server log, so what goes wrong in the shutdown client?

      Shutting down server http://localhost:80
      java.net.ConnectException: Connection refused
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
      at java.net.Socket.connect(Socket.java:452)
      at java.net.Socket.connect(Socket.java:402)
      at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
      at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
      at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:814)
      at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:711)
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
      at java.net.URLConnection.getContent(URLConnection.java:585)
      at org.jboss.Shutdown.shutdown(Shutdown.java:105)
      at org.jboss.Shutdown.main(Shutdown.java:81)
      Shutdown complete

        • 1. Re: Exception on shutdown?
          Jon Barnett Master

          It looks like it tried to connect to a service to send another shutdown command but the service is no longer available - because the server has shut down after the first shutdown command. I've seem to recall that problem with the 3.0.x systems - perhaps an incorrect parameter passed to the shutdown script? I can't remember the exact reason. Most people probably got around this by using a process kill rather than using the shutdown client - I think the go.sh script works along those lines.

          In 3.2.x, this problem does not occur for shutdown.sh running on the same platform.