hi hannah, even we were getting the same problem i.e. Dr. Watson which was very irritating. from which ever machine we did Dr. Watson would come up. we were also doing everything right, closing the connections, using oracle thin driver, returning the connection back to the pool. after all this we just reinstalled the jdk. and didnt get the problem again. why dont u also try reinstalling the jdk.
Vikramjit Singh, Systems Engineer, GTL Ltd. Ph. 7612929-3140 -----Original Message----- From: Hannah Liebe [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 9:54 PM To: [EMAIL PROTECTED] Subject: JVM crash with JRun 3.02 We are developing a JSP/Servlet/Java bean based application and use JRun 3.02a.11614 as the JSP/Servlet engine on top of IIS 4.0/NT 4.0 using either the Sun JVM 1.3.0.02 or JVM 1.3.1(see same crashing behaviour with either JVM) I've scoured the JSP-INTEREST archives and have confirmed the following: 1) not using the Sun JDBC-ODBC driver(we are using the Oracle thin driver oracle.jdbc.driver.OracleDriver) 2) PreparedStatement, ResultSet must always be closed 3) connections must always be returned to the pool (Would a single connection not returned to the pool or single unclosed statment be enough to crash the JVM? It is a large site with many JSP files and beans.) We are experiencing these significant problems: - Browsing through our JSP pages often results in a JVM crash (a bad one!). We get "javaw.exe - Application Error Access Memory Violations ...Instruction referenced memory ...." which is caught by Dr. Watson. This seems to happen after the JRun has been running several hours but scouring the log files has not yielded any specific JSP page which could be causing the problem(seems to be random). From the server console, we see drwatson dialogue box with the "javaw.exe" error and the "dontdiejava.exe" error which indicates that the memory contents are being dumped to a 500MB dump file. - Sometimess we see a "java.lang.OutOfMemory <<no stack trace available>>" error in the JRun log files (but not every time the JVM crashes). From the browser we sometimes get an OutOfMemory error as well. Not sure if the OutOfMemory exception is related or not. This may be a separate problem which also causes the JVM to crash - We've seen these error messages in the log file occassionally: # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 4349254E560E43505000F4 # # Problematic Thread: prio=5 tid=0x449ad0 nid=0x57 runnable # # HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Error ID: 4F533F57494E13120E43505002D4 # -These problems have been reported to Sun but they have only recommended upgrading the JVM to 1.3.1.02 or 1.4Beta since we cannot identify an exact causal sequence Any suggestions? Anyone had similar behavior? __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.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 =========================================================================== 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
