Environment: IIS 4.0 on NT 4.0 with JRun 3.02 and Sun JVM 1.3.1_02(configured to 512 MB) After site has been running several hours, JRun serves up a "JRun closed connection" error message for most JSP requests.
"JRun connector protocol error" "JRun closed connection" It is not clear what exactly causes this fatal error but afterwords JRun serves up the "JRun closed connection" error for most JSP pages on the site. It seems that IIS is still up and thinks it is serving the JSP page since the log shows 200 HTTP status which makes is hard to tell exactly which request has caused the fatal closed connection error: 2002-02-08 GET /index.jsp 200 335 1494 16 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+6.0b;+Windows+NT+5.0) It looks like JVM process (javaw.exe) and JRun (jrun.exe) are sill running on NT and process size of javaw.exe is far below 512MB max (so probably not the java.lang.OutOfMemory problem that we have also seen on site) Has anyone seen this problem ? Has anyone tried JRun version 3.1 with cumulative patch and seen improvement in the JRun/IIS connection? __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
