Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
JTurbo Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 189
Product ServletExec
Category Miscellaneous
Question When I run the StopServletExec script, I sometimes see an error. What does this mean ?
Answer When SE AS is NOT running, and you try to stop it by invoking the StopServletExec.bat file directly in a DOS window, StopServletExec.bat will say:
ERROR: Received an i/o exception - java.net.ConnectException: Connection refused: connect
ERROR: Failed to stop ServletExec.

The most common causes of this are:
  1. Your ServletExec AS instance was not running to begin with.
  2. Your StopServletExec script is using the wrong port (it must be the same port being used by your SE instance).
This is not a problem with ServletExec.

If you are using SE AS 4.x, and your SE AS instance IS running, and you try to stop it by invoking the StopServletExec.bat file directly in a DOS window, then StopServletExec.bat will give a slightly different error message:
ERROR: Received an i/o exception - java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
ERROR: Failed to stop ServletExec.

This is a bug in the StopServletExec program (not ServletExec), and can safely be ignored. In this case, ServletExec does correctly shutdown despite what the message says.
On a windows machine, most users run ServletExec AS as a windows Service (which calls the StartServletExec.bat and StopServletExec.bat scripts for you under the covers). So, the only way you would ever see any output from either of these scripts is if you manually invoke them from the command prompt.
This problem will be fixed in SE 5.0



   
company media information terms of use privacy policy contact us