We are using ServletExec V4.2 (ISAPI in process plugin) to deploy a servlet on microsoft IIS server. The servlet, a third party reporting tool works fine for a while and then we start seeing connection timeouts. The timeout problems disappear once we reload the "Web application" from the servlet administration utility on the server. This same setup has been installed on other servers and has been working without any issues. I would appreciate if anyone can throw some light on why this is happening.
ServletExec: V4.2 (ISAPI plugin) JDK: JDK V 1.4.1_03 (currentVersion) JRE: JRE V1.4.1_03, JRE V1.5.0_18 (currentVersion) Windows Server 2003 IIS Version 6.0
Snippet of the error from servletExec log files: at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:274) at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:191) at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1390) at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:1243) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1235) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1113) Caused by: java.net.ConnectException: Connection timed out: connect 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:434) at java.net.Socket.connect(Socket.java:384)
The first issue I see is that you are running ServletExec 4.2 on an unsupported version of Windows. SE 4.2 does not support Windows 2003.
While it may be possible to point to other Win 2003 systems that seem to successfully run SE 4.2, please understand that those systems are time bombs which could fail in any of several different ways at any moment, for seemingly unknown reasons.
PS It is entirely possible that you will still encounter this same issue even after switching from SE ISAPI to SE AS, but at least then you will be running on a supported platform and will have significantly narrowed down the possible causes of the problem.
Thanks for your prompt and in-depth response.The "ServletExec" came bundled with the reporting solution we have and I was never aware of the compatibility requirements. I will take it back to my team and consider our options.