can tomcat 5.5.9 inc compatibility pack but over jdk1.5 cause a jvm crash?
hello; i have a tomcat 5.5.9 over jdk 1.5 on freeBSD running a web application. i got the crash below. note that i noticed that my 5.5.9 was started with the compatibility package inside (i forgot to remove it). but my question is: can such a jvm crash be caused by this? thanks in advance. crash stack trace: # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGBUS (0xa) at pc=0x28261710, pid=85917, tid=0x82ec800 # # Java VM: Java HotSpot(TM) Client VM (1.5.0-p1-root_08_apr_2005_11_21 mixed mode) # Problematic frame: # V [libjvm.so+0x138710] # # An error report file with more information is saved as hs_err_pid85917.log # # If you would like to submit a bug report, please write # a letter to [EMAIL PROTECTED] mailing list # Guy Katz Allot Communications [EMAIL PROTECTED] tel: +972 9 7619288 fax: +972 9 7443626
Re: JVM Crash
Mark wrote: I googled around and here some good(?) news, at least somebody get around the problem: http://forum.java.sun.com/thread.jspa?threadID=307252&tstart=210 on of solution is : -- cut -- now I use jdk1.3.1_06 with hospot -server and it works perfectly (and faster) -- end cut --- another one was a hardware problem: -- cut -- Some part of the computer seemed to be not compatible with the FSB133 standard. So I reduced the system to FSB100. No signal 11 since that time :- -- end cut -- and here another issue with java: -- cut -- In this case, it was happening during the compilation of a reasonably large JSP. A colleague found out that there was a known issue with this version of javac compiling large methods (>64Kb), which tends to happen when you have a large JSP getting compiled into a single service() method. -- end cut -- --- Amit Gupta <[EMAIL PROTECTED]> wrote: I am facing similar problem on user mode Linux. Amit Gupta Mobile: 91-9818052171 Yahoo IM: amitguptainn MSN IM : amitguptainn -Original Message- From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 5:05 PM To: Tomcat Users List Subject: Re: JVM Crash Amit, I am using a dedicated server. Rodrigo Amit Gupta wrote: You are using User mode Linux or dedicated server? Amit Gupta Mobile: 91-9818052171 -Original Message- From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, December 27, 2004 11:18 PM To: tomcat-user@jakarta.apache.org Subject: JVM Crash Hello all, I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I experienced two random JVM crashes in a period of one month. The strange part is that the crashes occured when the application was at a very low load, doing almost nothing. I searched the archives for this topic, but I still can't figure out what could have caused these crashes. I have no idea whether they are related to Jira, Tomcat, J2SDK or RedHat. I would like to isolate the problem, so that I can ask the proper vendor for support. Below I will post information about my system and the JVM error logs, sorry for the long message. Any help is greatly appreciated, thanks a lot. Rodrigo System: Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon) Tomcat 5.0.28 java version "1.4.2_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) JAVA_OPTS="-server -Xmx512m" 1GB RAM CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 Error log 1: Unexpected Signal : 11 occurred at PC=0xB7289E78 Function=(null) Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.String.intern(Native Method) at java.lang.Class.searchMethods(Class.java:1877) at java.lang.Class.getDeclaredMethod(Class.java:1262) at org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) at org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) at org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) at org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) at org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) - locked <0x925030d0> (a org.apache.commons.beanutils.BeanUtilsBean$1) at org.apache.commons.beanutils.BeanUtilsBean.getInstance(BeanUtilsBean.java:78) - locked <0xaeeb91a0> (a java.lang.Class) at org.apache.commons.beanutils.ConvertUtilsBean.getInstance(ConvertUtilsBean.java:115) at org.apache.commons.beanutils.ConvertUtils.convert(ConvertUtils.java:217) at org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:457) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
RE: JVM Crash
I googled around and here some good(?) news, at least somebody get around the problem: http://forum.java.sun.com/thread.jspa?threadID=307252&tstart=210 on of solution is : -- cut -- now I use jdk1.3.1_06 with hospot -server and it works perfectly (and faster) -- end cut --- another one was a hardware problem: -- cut -- Some part of the computer seemed to be not compatible with the FSB133 standard. So I reduced the system to FSB100. No signal 11 since that time :- -- end cut -- and here another issue with java: -- cut -- In this case, it was happening during the compilation of a reasonably large JSP. A colleague found out that there was a known issue with this version of javac compiling large methods (>64Kb), which tends to happen when you have a large JSP getting compiled into a single service() method. -- end cut -- --- Amit Gupta <[EMAIL PROTECTED]> wrote: > I am facing similar problem on user mode Linux. > > Amit Gupta > Mobile: 91-9818052171 > Yahoo IM: amitguptainn > MSN IM : amitguptainn > > -Original Message- > From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 28, 2004 5:05 PM > To: Tomcat Users List > Subject: Re: JVM Crash > > Amit, I am using a dedicated server. > > Rodrigo > > Amit Gupta wrote: > > >You are using User mode Linux or dedicated server? > > > >Amit Gupta > >Mobile: 91-9818052171 > > > >-Original Message- > >From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] > >Sent: Monday, December 27, 2004 11:18 PM > >To: tomcat-user@jakarta.apache.org > >Subject: JVM Crash > > > >Hello all, > > > >I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I > >experienced two random JVM crashes in a period of one month. The > strange > >part is that the crashes occured when the application was at a > very low > >load, doing almost nothing. > >I searched the archives for this topic, but I still can't figure > out > >what could have caused these crashes. > >I have no idea whether they are related to Jira, Tomcat, J2SDK or > >RedHat. I would like to isolate the problem, so that I can ask the > > >proper vendor for support. > >Below I will post information about my system and the JVM error > logs, > >sorry for the long message. > >Any help is greatly appreciated, thanks a lot. > > > >Rodrigo > > > >System: > >Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 > GNU/Linux > >Red Hat Enterprise Linux AS release 3 (Taroon) > >Tomcat 5.0.28 > >java version "1.4.2_06" > >Java(TM) 2 Runtime Environment, Standard Edition (build > 1.4.2_06-b03) > >Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) > >JAVA_OPTS="-server -Xmx512m" > >1GB RAM > >CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 > > > >Error log 1: > >Unexpected Signal : 11 occurred at PC=0xB7289E78 > >Function=(null) > >Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so > > > >NOTE: We are unable to locate the function name symbol for the > error > > just occurred. Please refer to release documentation for > possible > > reason and solutions. > > > > > >Current Java thread: > >at java.lang.String.intern(Native Method) > >at java.lang.Class.searchMethods(Class.java:1877) > >at java.lang.Class.getDeclaredMethod(Class.java:1262) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) > >at > >org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) > >at > org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) > >at > >org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) > >at > >org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) > >at > >org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) > >at > >org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) > >- locked <
RE: JVM Crash
I am facing similar problem on user mode Linux. Amit Gupta Mobile: 91-9818052171 Yahoo IM: amitguptainn MSN IM : amitguptainn -Original Message- From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 28, 2004 5:05 PM To: Tomcat Users List Subject: Re: JVM Crash Amit, I am using a dedicated server. Rodrigo Amit Gupta wrote: >You are using User mode Linux or dedicated server? > >Amit Gupta >Mobile: 91-9818052171 > >-Original Message- >From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] >Sent: Monday, December 27, 2004 11:18 PM >To: tomcat-user@jakarta.apache.org >Subject: JVM Crash > >Hello all, > >I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I >experienced two random JVM crashes in a period of one month. The strange >part is that the crashes occured when the application was at a very low >load, doing almost nothing. >I searched the archives for this topic, but I still can't figure out >what could have caused these crashes. >I have no idea whether they are related to Jira, Tomcat, J2SDK or >RedHat. I would like to isolate the problem, so that I can ask the >proper vendor for support. >Below I will post information about my system and the JVM error logs, >sorry for the long message. >Any help is greatly appreciated, thanks a lot. > >Rodrigo > >System: >Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux >Red Hat Enterprise Linux AS release 3 (Taroon) >Tomcat 5.0.28 >java version "1.4.2_06" >Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) >Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) >JAVA_OPTS="-server -Xmx512m" >1GB RAM >CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 > >Error log 1: >Unexpected Signal : 11 occurred at PC=0xB7289E78 >Function=(null) >Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so > >NOTE: We are unable to locate the function name symbol for the error > just occurred. Please refer to release documentation for possible > reason and solutions. > > >Current Java thread: >at java.lang.String.intern(Native Method) >at java.lang.Class.searchMethods(Class.java:1877) >at java.lang.Class.getDeclaredMethod(Class.java:1262) >at >org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) >at >org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) >at >org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) >at >org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) >at >org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) >at >org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) >at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) >at >org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) >at >org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) >at >org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) >at >org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) >- locked <0x925030d0> (a >org.apache.commons.beanutils.BeanUtilsBean$1) >at >org.apache.commons.beanutils.BeanUtilsBean.getInstance(BeanUtilsBean.java:78) >- locked <0xaeeb91a0> (a java.lang.Class) >at >org.apache.commons.beanutils.ConvertUtilsBean.getInstance(ConvertUtilsBean.java:115) >at >org.apache.commons.beanutils.ConvertUtils.convert(ConvertUtils.java:217) >at >org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:457) >at org.apache.commons.digester.Rule.end(Rule.java:276) >at >org.apache.commons.digester.Digester.endElement(Digester.java:1058) >at >org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) >at >org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown >Source) >at >org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > >Source) >at >org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown >Source) >at org.apache.xerces.parsers.XML11Configuration.parse(Unknown >Source) >at org.apache.xerces.parsers.XML11Configuration.parse(Unknown >Source) >at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) >at org.apache.xerces.parsers.AbstractSAXParser.parse(Unkno
Re: JVM Crash
Amit, I am using a dedicated server. Rodrigo Amit Gupta wrote: You are using User mode Linux or dedicated server? Amit Gupta Mobile: 91-9818052171 -Original Message- From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, December 27, 2004 11:18 PM To: tomcat-user@jakarta.apache.org Subject: JVM Crash Hello all, I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I experienced two random JVM crashes in a period of one month. The strange part is that the crashes occured when the application was at a very low load, doing almost nothing. I searched the archives for this topic, but I still can't figure out what could have caused these crashes. I have no idea whether they are related to Jira, Tomcat, J2SDK or RedHat. I would like to isolate the problem, so that I can ask the proper vendor for support. Below I will post information about my system and the JVM error logs, sorry for the long message. Any help is greatly appreciated, thanks a lot. Rodrigo System: Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon) Tomcat 5.0.28 java version "1.4.2_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) JAVA_OPTS="-server -Xmx512m" 1GB RAM CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 Error log 1: Unexpected Signal : 11 occurred at PC=0xB7289E78 Function=(null) Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.String.intern(Native Method) at java.lang.Class.searchMethods(Class.java:1877) at java.lang.Class.getDeclaredMethod(Class.java:1262) at org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) at org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) at org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) at org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) at org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) - locked <0x925030d0> (a org.apache.commons.beanutils.BeanUtilsBean$1) at org.apache.commons.beanutils.BeanUtilsBean.getInstance(BeanUtilsBean.java:78) - locked <0xaeeb91a0> (a java.lang.Class) at org.apache.commons.beanutils.ConvertUtilsBean.getInstance(ConvertUtilsBean.java:115) at org.apache.commons.beanutils.ConvertUtils.convert(ConvertUtils.java:217) at org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:457) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.ContextConfig.defaultConfig(ContextConfig.java:515) - locked <0x92641798> (a org.apache.commons.digester.Digester) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:623) - locked <0x93a28f98> (a org.apache.catalina.startup.ContextConfig) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:216) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4290) - locked <0x93a119f0>
RE: JVM Crash
You are using User mode Linux or dedicated server? Amit Gupta Mobile: 91-9818052171 -Original Message- From: Rodrigo Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, December 27, 2004 11:18 PM To: tomcat-user@jakarta.apache.org Subject: JVM Crash Hello all, I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I experienced two random JVM crashes in a period of one month. The strange part is that the crashes occured when the application was at a very low load, doing almost nothing. I searched the archives for this topic, but I still can't figure out what could have caused these crashes. I have no idea whether they are related to Jira, Tomcat, J2SDK or RedHat. I would like to isolate the problem, so that I can ask the proper vendor for support. Below I will post information about my system and the JVM error logs, sorry for the long message. Any help is greatly appreciated, thanks a lot. Rodrigo System: Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon) Tomcat 5.0.28 java version "1.4.2_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) JAVA_OPTS="-server -Xmx512m" 1GB RAM CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 Error log 1: Unexpected Signal : 11 occurred at PC=0xB7289E78 Function=(null) Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.String.intern(Native Method) at java.lang.Class.searchMethods(Class.java:1877) at java.lang.Class.getDeclaredMethod(Class.java:1262) at org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) at org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) at org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) at org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) at org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) - locked <0x925030d0> (a org.apache.commons.beanutils.BeanUtilsBean$1) at org.apache.commons.beanutils.BeanUtilsBean.getInstance(BeanUtilsBean.java:78) - locked <0xaeeb91a0> (a java.lang.Class) at org.apache.commons.beanutils.ConvertUtilsBean.getInstance(ConvertUtilsBean.java:115) at org.apache.commons.beanutils.ConvertUtils.convert(ConvertUtils.java:217) at org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:457) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.ContextConfig.defaultConfig(ContextConfig.java:515) - locked <0x92641798> (a org.apache.commons.digester.Digester) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:623) - locked <0x93a28f98> (a org.apache.catalina.startup.ContextConfig) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:216) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4290) - locked <0x93a119f0>
Re: JVM Crash
Rodrigo Schmidt wrote: Hi Wade, thanks for your reply. I already reported the bug, but they can take a long time to send an answer. Searching the bug database I found some posts that reported the problem happening with the client vm as well. I am considering trying another vm. I've just tested BEA JRockit 1.4.2_05, but it seems that Jira doesn't like it that much, or vice-versa : ) So, does anyone has experience with Tomcat 5.0.x running on JDK 1.5? Are there performace/stability issues? Thanks in advance, Rodrigo Wade Chandler wrote: Wade Chandler wrote: Rodrigo Schmidt wrote: Local Time = Sun Dec 26 13:39:24 2004 Elapsed Time = 437787 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002EF # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_06-b03 mixed mode) # From the logs it looks like some code is exploiting a bug in the JVM. The first place I would search is the JVM bug database... http://bugs.sun.com/bugdatabase/index.jsp See if you can find anything relative to the information given. Also look for the error id. The next thing to do if you do not find the bug is to report it. You can find other options to fix the issue here: http://bugs.sun.com/services/bugreport/index.jsp Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Looking at the bugreports it looks like you might try to drop the -server from your startup and see if you can at least stay up and running. All the bug reports I saw for this error were caused by the server vm. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I'm not sure if version 5.0.x will run with JDK1.5 or not. I think I've seen where it will not. I might be wrong. It might have been 5.5.x won't run on 1.4.x vms If I were you I would try not specifying server and at least see how it behaves before I tried something else. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JVM Crash
Hi Wade, thanks for your reply. I already reported the bug, but they can take a long time to send an answer. Searching the bug database I found some posts that reported the problem happening with the client vm as well. I am considering trying another vm. I've just tested BEA JRockit 1.4.2_05, but it seems that Jira doesn't like it that much, or vice-versa : ) So, does anyone has experience with Tomcat 5.0.x running on JDK 1.5? Are there performace/stability issues? Thanks in advance, Rodrigo Wade Chandler wrote: Wade Chandler wrote: Rodrigo Schmidt wrote: Local Time = Sun Dec 26 13:39:24 2004 Elapsed Time = 437787 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002EF # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_06-b03 mixed mode) # From the logs it looks like some code is exploiting a bug in the JVM. The first place I would search is the JVM bug database... http://bugs.sun.com/bugdatabase/index.jsp See if you can find anything relative to the information given. Also look for the error id. The next thing to do if you do not find the bug is to report it. You can find other options to fix the issue here: http://bugs.sun.com/services/bugreport/index.jsp Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Looking at the bugreports it looks like you might try to drop the -server from your startup and see if you can at least stay up and running. All the bug reports I saw for this error were caused by the server vm. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JVM Crash
Wade Chandler wrote: Rodrigo Schmidt wrote: Local Time = Sun Dec 26 13:39:24 2004 Elapsed Time = 437787 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002EF # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_06-b03 mixed mode) # From the logs it looks like some code is exploiting a bug in the JVM. The first place I would search is the JVM bug database... http://bugs.sun.com/bugdatabase/index.jsp See if you can find anything relative to the information given. Also look for the error id. The next thing to do if you do not find the bug is to report it. You can find other options to fix the issue here: http://bugs.sun.com/services/bugreport/index.jsp Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Looking at the bugreports it looks like you might try to drop the -server from your startup and see if you can at least stay up and running. All the bug reports I saw for this error were caused by the server vm. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JVM Crash
Rodrigo Schmidt wrote: Local Time = Sun Dec 26 13:39:24 2004 Elapsed Time = 437787 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002EF # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_06-b03 mixed mode) # From the logs it looks like some code is exploiting a bug in the JVM. The first place I would search is the JVM bug database... http://bugs.sun.com/bugdatabase/index.jsp See if you can find anything relative to the information given. Also look for the error id. The next thing to do if you do not find the bug is to report it. You can find other options to fix the issue here: http://bugs.sun.com/services/bugreport/index.jsp Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JVM Crash
Hello all, I deployed Atlassian Jira Enterprise 3.0.3 in Tomcat 5.0.28 and I experienced two random JVM crashes in a period of one month. The strange part is that the crashes occured when the application was at a very low load, doing almost nothing. I searched the archives for this topic, but I still can't figure out what could have caused these crashes. I have no idea whether they are related to Jira, Tomcat, J2SDK or RedHat. I would like to isolate the problem, so that I can ask the proper vendor for support. Below I will post information about my system and the JVM error logs, sorry for the long message. Any help is greatly appreciated, thanks a lot. Rodrigo System: Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon) Tomcat 5.0.28 java version "1.4.2_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) Java HotSpot(TM) Server VM (build 1.4.2_06-b03, mixed mode) JAVA_OPTS="-server -Xmx512m" 1GB RAM CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 Error log 1: Unexpected Signal : 11 occurred at PC=0xB7289E78 Function=(null) Library=/usr/local/j2sdk1.4.2_06/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.String.intern(Native Method) at java.lang.Class.searchMethods(Class.java:1877) at java.lang.Class.getDeclaredMethod(Class.java:1262) at org.apache.commons.logging.impl.LogFactoryImpl.isJdk14Available(LogFactoryImpl.java:489) at org.apache.commons.logging.impl.LogFactoryImpl.getLogClassName(LogFactoryImpl.java:331) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:368) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:130) at org.apache.commons.beanutils.BeanUtilsBean.(BeanUtilsBean.java:110) at org.apache.commons.beanutils.BeanUtilsBean$1.initialValue(BeanUtilsBean.java:68) at org.apache.commons.beanutils.ContextClassLoaderLocal.get(ContextClassLoaderLocal.java:80) - locked <0x925030d0> (a org.apache.commons.beanutils.BeanUtilsBean$1) at org.apache.commons.beanutils.BeanUtilsBean.getInstance(BeanUtilsBean.java:78) - locked <0xaeeb91a0> (a java.lang.Class) at org.apache.commons.beanutils.ConvertUtilsBean.getInstance(ConvertUtilsBean.java:115) at org.apache.commons.beanutils.ConvertUtils.convert(ConvertUtils.java:217) at org.apache.commons.digester.CallMethodRule.end(CallMethodRule.java:457) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.ContextConfig.defaultConfig(ContextConfig.java:515) - locked <0x92641798> (a org.apache.commons.digester.Digester) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:623) - locked <0x93a28f98> (a org.apache.catalina.startup.ContextConfig) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:216) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4290) - locked <0x93a119f0> (a org.apache.catalina.core.StandardContext) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) - locked <0x92598d40> (a java.util.HashMap) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) at org.apache.catalina.core.StandardHostDeployer.insta
Re: Tomcat 4.1.29 JVM crash on RHEL-3-ES
Joe, I'm experiencing sporadic crashing of the JVM running Tomcat in 2 of my environments. These environments both run the same webapps, and they both use JDK 1.4.2_03 on RHEL-3 ES. Other environments where these same webapps run are using JDK 1.4.1 and Redhat7.2, and are not experiencing these crashes. What kernel version are you using (I assume you're using 2.4.something). There's a lot of talk on this list about having to set the LD_ASSUME_KERNEL environment variable in order to prevent crashes like these on various versions of Linux (esp. RedHat). I myself have never needed this setting. Do a quick search in the archives for LD_ASSUME and see whet they have to say. -chris signature.asc Description: OpenPGP digital signature
RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES
Did you go thru some profilers. 1. Which version of JVM you are running. 2. What is your hardware OS. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 3:04 PM To: Tomcat Users List Cc: 'Tomcat Users List' Subject: RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES The servers are only being used internally for testing at the moment. As best I can tell, the crashes occur at night when nothing (or very few people) are using the them. > Original Message > Subject: RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES > From: "Kannan Sundararajan" <[EMAIL PROTECTED]> > Date: Mon, March 01, 2004 11:53 am > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > > Did you load test these servers? > > -Original Message- > From: Joe Miller [mailto:[EMAIL PROTECTED] > Sent: Monday, March 01, 2004 1:37 PM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1.29 JVM crash on RHEL-3-ES > > > Hello, > > I'm experiencing sporadic crashing of the JVM running Tomcat in 2 of > my > environments. These environments both run the same webapps, and they > both > use JDK 1.4.2_03 on RHEL-3 ES. Other environments where these same > webapps > run are using JDK 1.4.1 and Redhat7.2, and are not experiencing these > crashes. > > The crashes appear to happen at random times and hours. Currently > these > webapps are very lightly used, and most likely completely unused when > the > crashes occur. > > Has anyone experienced this with a similar setup? > > My CATALINA_OPTS: > CATALINA_OPTS="-Xms2548m -Xmx2548m -server" > > All I see in Catalina.out is the following. Messages preceding this VM > dump > message are different each time. > > # > # HotSpot Virtual Machine Error, Internal Error > # Please report this error at > # http://java.sun.com/cgi-bin/bugreport.cgi > # > # Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 mixed mode) > # > # Error ID: 53484152454432554E54494D450E435050018D > # > # Problematic Thread: prio=1 tid=0x085062c8 nid=0x22c5 runnable > # > > Heap at VM Abort: > Heap > def new generation total 260928K, used 132963K [0x0f7f, > 0x2130, > 0x2130) > eden space 232000K, 53% used [0x0f7f, 0x170acf50, 0x1da8) > to space 28928K, 0% used [0x1f6c, 0x1f6c, 0x2130) > tenured generation total 2319296K, used 46617K [0x2130, > 0xaebf, > 0xaebf) >the space 2319296K, 2% used [0x2130, 0x240865e8, 0x24086600, > 0xaebf) > compacting perm gen total 26112K, used 26092K [0xaebf, > 0xb057, > 0xb2bf) >the space 26112K, 99% used [0xaebf, 0xb056b260, 0xb056b400, > 0xb057) > > > > -- > Joe Miller > Linux Administrator > GoDaddy.com > [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES
The servers are only being used internally for testing at the moment. As best I can tell, the crashes occur at night when nothing (or very few people) are using the them. > Original Message > Subject: RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES > From: "Kannan Sundararajan" <[EMAIL PROTECTED]> > Date: Mon, March 01, 2004 11:53 am > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > > Did you load test these servers? > > -Original Message- > From: Joe Miller [mailto:[EMAIL PROTECTED] > Sent: Monday, March 01, 2004 1:37 PM > To: [EMAIL PROTECTED] > Subject: Tomcat 4.1.29 JVM crash on RHEL-3-ES > > > Hello, > > I'm experiencing sporadic crashing of the JVM running Tomcat in 2 of > my > environments. These environments both run the same webapps, and they > both > use JDK 1.4.2_03 on RHEL-3 ES. Other environments where these same > webapps > run are using JDK 1.4.1 and Redhat7.2, and are not experiencing these > crashes. > > The crashes appear to happen at random times and hours. Currently > these > webapps are very lightly used, and most likely completely unused when > the > crashes occur. > > Has anyone experienced this with a similar setup? > > My CATALINA_OPTS: > CATALINA_OPTS="-Xms2548m -Xmx2548m -server" > > All I see in Catalina.out is the following. Messages preceding this VM > dump > message are different each time. > > # > # HotSpot Virtual Machine Error, Internal Error > # Please report this error at > # http://java.sun.com/cgi-bin/bugreport.cgi > # > # Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 mixed mode) > # > # Error ID: 53484152454432554E54494D450E435050018D > # > # Problematic Thread: prio=1 tid=0x085062c8 nid=0x22c5 runnable > # > > Heap at VM Abort: > Heap > def new generation total 260928K, used 132963K [0x0f7f, > 0x2130, > 0x2130) > eden space 232000K, 53% used [0x0f7f, 0x170acf50, 0x1da8) > to space 28928K, 0% used [0x1f6c, 0x1f6c, 0x2130) > tenured generation total 2319296K, used 46617K [0x2130, > 0xaebf, > 0xaebf) >the space 2319296K, 2% used [0x2130, 0x240865e8, 0x24086600, > 0xaebf) > compacting perm gen total 26112K, used 26092K [0xaebf, > 0xb057, > 0xb2bf) >the space 26112K, 99% used [0xaebf, 0xb056b260, 0xb056b400, > 0xb057) > > > > -- > Joe Miller > Linux Administrator > GoDaddy.com > [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.1.29 JVM crash on RHEL-3-ES
Did you load test these servers? -Original Message- From: Joe Miller [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 1:37 PM To: [EMAIL PROTECTED] Subject: Tomcat 4.1.29 JVM crash on RHEL-3-ES Hello, I'm experiencing sporadic crashing of the JVM running Tomcat in 2 of my environments. These environments both run the same webapps, and they both use JDK 1.4.2_03 on RHEL-3 ES. Other environments where these same webapps run are using JDK 1.4.1 and Redhat7.2, and are not experiencing these crashes. The crashes appear to happen at random times and hours. Currently these webapps are very lightly used, and most likely completely unused when the crashes occur. Has anyone experienced this with a similar setup? My CATALINA_OPTS: CATALINA_OPTS="-Xms2548m -Xmx2548m -server" All I see in Catalina.out is the following. Messages preceding this VM dump message are different each time. # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 mixed mode) # # Error ID: 53484152454432554E54494D450E435050018D # # Problematic Thread: prio=1 tid=0x085062c8 nid=0x22c5 runnable # Heap at VM Abort: Heap def new generation total 260928K, used 132963K [0x0f7f, 0x2130, 0x2130) eden space 232000K, 53% used [0x0f7f, 0x170acf50, 0x1da8) to space 28928K, 0% used [0x1f6c, 0x1f6c, 0x2130) tenured generation total 2319296K, used 46617K [0x2130, 0xaebf, 0xaebf) the space 2319296K, 2% used [0x2130, 0x240865e8, 0x24086600, 0xaebf) compacting perm gen total 26112K, used 26092K [0xaebf, 0xb057, 0xb2bf) the space 26112K, 99% used [0xaebf, 0xb056b260, 0xb056b400, 0xb057) -- Joe Miller Linux Administrator GoDaddy.com [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1.29 JVM crash on RHEL-3-ES
Hello, I'm experiencing sporadic crashing of the JVM running Tomcat in 2 of my environments. These environments both run the same webapps, and they both use JDK 1.4.2_03 on RHEL-3 ES. Other environments where these same webapps run are using JDK 1.4.1 and Redhat7.2, and are not experiencing these crashes. The crashes appear to happen at random times and hours. Currently these webapps are very lightly used, and most likely completely unused when the crashes occur. Has anyone experienced this with a similar setup? My CATALINA_OPTS: CATALINA_OPTS="-Xms2548m -Xmx2548m -server" All I see in Catalina.out is the following. Messages preceding this VM dump message are different each time. # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 mixed mode) # # Error ID: 53484152454432554E54494D450E435050018D # # Problematic Thread: prio=1 tid=0x085062c8 nid=0x22c5 runnable # Heap at VM Abort: Heap def new generation total 260928K, used 132963K [0x0f7f, 0x2130, 0x2130) eden space 232000K, 53% used [0x0f7f, 0x170acf50, 0x1da8) to space 28928K, 0% used [0x1f6c, 0x1f6c, 0x2130) tenured generation total 2319296K, used 46617K [0x2130, 0xaebf, 0xaebf) the space 2319296K, 2% used [0x2130, 0x240865e8, 0x24086600, 0xaebf) compacting perm gen total 26112K, used 26092K [0xaebf, 0xb057, 0xb2bf) the space 26112K, 99% used [0xaebf, 0xb056b260, 0xb056b400, 0xb057) -- Joe Miller Linux Administrator GoDaddy.com [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: debugging tomcat/jvm crash
I ran Tomcat from the console, when the JVM crashed I got the following message: Another exception has been detected while we were handling last error. Dumping information about last error: ERROR REPORT FILE = (N/A) PC= 0x2BE5C46D SIGNAL= -1073741819 FUNCTION NAME = (N/A) OFFSET= 0x LIBRARY NAME = (N/A) Please check ERROR REPORT FILE for further information, if there is any. Good bye. Anyone know why this might occur or how to get the JVM to write to the error report file? Thanks. Quoting [EMAIL PROTECTED]: > i have been experiencing a serious crash running my webapp on > tomcat4.1.18 + > j2sdk1.4.1_02 + win2k. the tomcat/java process completely disappears > without a > trace. nothing is left in any of the logs suggesting what caused the > crash and > we are unable to reproduce it in our testing environment. > > can anybody give me some advice on how i can get more information on > what is > causing the crash. on a un*x os i would expect a core file to be left > behind > after a crash. does anyone know how it is possible to get that kind of > crash > data out of java on win2k? > > thanks, > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
debugging tomcat/jvm crash
i have been experiencing a serious crash running my webapp on tomcat4.1.18 + j2sdk1.4.1_02 + win2k. the tomcat/java process completely disappears without a trace. nothing is left in any of the logs suggesting what caused the crash and we are unable to reproduce it in our testing environment. can anybody give me some advice on how i can get more information on what is causing the crash. on a un*x os i would expect a core file to be left behind after a crash. does anyone know how it is possible to get that kind of crash data out of java on win2k? thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
More on 4.12 JVM crash -- Class loading multiple times
I have some more information regarding my app in 4.12 crashing the JVM (both
1.3 and 1.4. Both Server and Client).
Quick history is that I'm trying to port a WAR from 3.2 to 4.12, and the JVM
is faulting with an internal error.
I went and added
java -verbose:class -verbose:gc
in $JAVA_OPTS in order to get a glimpse of what's going on inside the JVM
before it explodes on us.
Initially, I found that the JVM was crashing while it was loading a
particular class. I determined this by seeing the [Loaded com.app.Class]
message from the -verbose:class option.
I changed that class by adding a dummy method to it and recompiling.
void dummyMethod() { }
On my next run, it seem to load that class ok, but the JVM still crashes
later on.
What I noticed at that point was that it was crashing after it had loaded a
class the SECOND time.
It looked like this:
[Loaded com.app.ClassA]
[Loaded com.app.ClassB]
[Loaded com.app.ClassA]
I did some quick analysis and found that several classes were "loading
twice".
How can this be? They're not being GCd away and then reloaded. Could it be
that two different class loaders are loading the same class, and that's what
this is showing?
Any pointers would be appreciated. I know I've been really fighting class
loader issues trying to port this application, so maybe it has something to
do with the JVM crashing.
Thanx!
Best Regards,
Will Hartung
([EMAIL PROTECTED])
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Re: Tomcat JVM crash
Wow...great... Thank's a lot :) This is exactly what I'm looking for. Alin - Original Message - From: "Bip Thelin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 11, 2001 5:21 PM Subject: Re: Tomcat JVM crash > On Fri, 11 May 2001, Alin Simionoiu wrote: > > > > [...] > > > > Second, the question was : How Tomcat handle JVM crashes, that's all. > > Filip send a very good answer : It doesn't..period. > > Ok, if the JVM dies tomcat dies, period. BUT In Tomcat 4 you have the > possibility to use a configurable Store to save Sessions. So you could > configure a FileStore or a JDBCStore to save Sessions due to the criterias > you set up. You could also use the StandardManager which attempts to save > Sessions across restarts or a jvm kill. However I would go with the > PersistentManager and either use File or JDBCStore. I suggest you pick > the latest Tomcat 4(4.4 as of writing) as the Store implementations have > grown more robust in the later releases. > > ..bip > >
Re: Tomcat JVM crash
On Fri, 11 May 2001, Alin Simionoiu wrote: > > [...] > > Second, the question was : How Tomcat handle JVM crashes, that's all. > Filip send a very good answer : It doesn't..period. Ok, if the JVM dies tomcat dies, period. BUT In Tomcat 4 you have the possibility to use a configurable Store to save Sessions. So you could configure a FileStore or a JDBCStore to save Sessions due to the criterias you set up. You could also use the StandardManager which attempts to save Sessions across restarts or a jvm kill. However I would go with the PersistentManager and either use File or JDBCStore. I suggest you pick the latest Tomcat 4(4.4 as of writing) as the Store implementations have grown more robust in the later releases. ..bip
Re: Tomcat JVM crash
First, If you don't want to answer, just don't.. I'm kinda become sick seeing every day "smart ..es".. Second, the question was : How Tomcat handle JVM crashes, that's all. Filip send a very good answer : It doesn't..period. BTW, for my application Tomcat is the second tier, not the first. - Original Message - From: "Greg Hanson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 11, 2001 2:59 PM Subject: RE: Tomcat JVM crash > First, use plain text when posting to this group, many of the users only > accept plain text. > > Second, for a scalable architecture that will be able to recover from > crashes or that need to save state, do not wholly rely upon Tomcat or any > other 1st tier platform. A suggestion would be to architect your system so > that the middle tier saves state (i.e. Stateful Session Bean). If tomcat > goes down, the middle ware will persist (so long as the middleware stays > up). > > You're asking a classic architectural question. Any others with > suggestions? > > > > -Original Message- > From: Alin Simionoiu [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 11, 2001 2:43 PM > To: [EMAIL PROTECTED] > Subject: Tomcat JVM crash > > > Does anybody know how Tomcat handle eventually JVM crash..? > I interested in this because I want to save some data between page, let's > say something like a shopping cart. > And I don't want to do this using hidden fields in page. > All this is in the some session. > Is JVM crash, and Tomcat start another one, or use another recovery > mechanism, then my data is lost. > > Any ideas? > > Thank you, > As >
RE: Tomcat JVM crash
First, use plain text when posting to this group, many of the users only accept plain text. Second, for a scalable architecture that will be able to recover from crashes or that need to save state, do not wholly rely upon Tomcat or any other 1st tier platform. A suggestion would be to architect your system so that the middle tier saves state (i.e. Stateful Session Bean). If tomcat goes down, the middle ware will persist (so long as the middleware stays up). You're asking a classic architectural question. Any others with suggestions? -Original Message- From: Alin Simionoiu [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 2:43 PM To: [EMAIL PROTECTED] Subject: Tomcat JVM crash Does anybody know how Tomcat handle eventually JVM crash..? I interested in this because I want to save some data between page, let's say something like a shopping cart. And I don't want to do this using hidden fields in page. All this is in the some session. Is JVM crash, and Tomcat start another one, or use another recovery mechanism, then my data is lost. Any ideas? Thank you, As
RE: Tomcat JVM crash
it doesn't handle it. if your vm dies, everything that is in it is gone. Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net -Original Message- From: Alin Simionoiu [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 2:43 PM To: [EMAIL PROTECTED] Subject: Tomcat JVM crash Does anybody know how Tomcat handle eventually JVM crash..? I interested in this because I want to save some data between page, let's say something like a shopping cart. And I don't want to do this using hidden fields in page. All this is in the some session. Is JVM crash, and Tomcat start another one, or use another recovery mechanism, then my data is lost. Any ideas? Thank you, As
Tomcat JVM crash
Does anybody know how Tomcat handle eventually JVM crash..? I interested in this because I want to save some data between page, let's say something like a shopping cart. And I don't want to do this using hidden fields in page. All this is in the some session. Is JVM crash, and Tomcat start another one, or use another recovery mechanism, then my data is lost. Any ideas? Thank you, As
