tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <mgai...@hotmail.com>
Subject Re: Tomcat Crashing -- how do I read the resulting hs_err_pid11598.log?
Date Fri, 21 Jul 2006 22:02:12 GMT
Kim-

Did you see this catch this bit of legalese in tiny print
Fedora Core 4 users are advised not to use the Java RPM provided by Sun. It contains Provides
that conflict with names used in packages provided as part of Fedora Core 4. Because of this,
Sun Java might disappear from an installed system during package upgrade operations. Fedora
Core 4 users should use either the RPM from jpackage.org or manually install the Sun Java
tarball into /opt. Sun Java 1.5+ is recommended for stability purposes. 

And also this ....
These packages have been modified in Fedora to remove proprietary software dependencies and
to make use of GCJ's ahead-of-time compilation feature

Apparently there exists some 'dependency' not only on package naming but another depdenency
on their ahead-of-time compiler..
Play it safe download from 
http://www.city-fan.org/tips/JpackageJava

and install the JVM from there..

HTH,
Martin --

*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



----- Original Message ----- 
From: "Kim Albee" <mtitania@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>; "Martin Gainty" <mgainty@hotmail.com>
Sent: Friday, July 21, 2006 5:17 PM
Subject: Re: Tomcat Crashing -- how do I read the resulting hs_err_pid11598.log?


> OS = Fedora Core 3 Linux with all updates from yum.
> Java version = 1.5.0_03
> Tomcat version 5.0.30
> ok -- here is the jvm.cfg:
> #
> # @(#)jvm.cfg   1.8 04/02/02
> #
> # Copyright 2003 Sun Microsystems, Inc. All rights reserved.
> # SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
> #
> #
> #
> #
> # List of JVMs that can be used as an option to java, javac, etc.
> # Order is important -- first in this list is the default JVM.
> # NOTE that this both this file and its format are UNSUPPORTED and
> # WILL GO AWAY in a future release.
> #
> # You may also select a JVM in an arbitrary location with the
> # "-XXaltjvm=<jvm_dir>" option, but that too is unsupported
> # and may not be available in a future release.
> #
> -client IF_SERVER_CLASS -server
> -server KNOWN
> -hotspot ALIASED_TO -client
> -classic WARN
> -native ERROR
> -green ERROR
> 
> 
> On 7/21/06, Martin Gainty <mgainty@hotmail.com> wrote:
>>
>> the hs_err_pid*.log is reminiscent of the Command and Control buttons on
>> the bridge of  the Starship Enterprise
>> In other words you cant tell what the different colored buttons mean
>> unless you read the 1000 page manual beforehand
>> (or in our case can talk to James Gosling!)
>>
>> so here goes..
>> siginfo: ExceptionCode=0xc0000005, reading address 0x00000004
>>
>> Registers:
>>
>> /*Generally the AX always has the returned code from the last operation*/
>> EAX=0x00000000, EBX=0x0764d168, ECX=0x07e04f1c, EDX=0x0849f7cc
>> ESP=0x0849f7d4, EBP=0x0849f838, ESI=0x07e04f1c, EDI=0x00000000
>> EIP=0x6d0e75d9, EFLAGS=0x00010246
>>
>> /*If you have a bright map showing all the locations of the variables and
>> their respective memory locations you could map the memory to the variable*/
>> Top of Stack: (sp=0x0849f7d4)
>> 0x0849f7d4: 0764d168 07e04f1c 00000000 6d0c7a0d
>> 0x0849f7e4: 20ae4238 20ae4238 07e04e60 0764d168
>> 0x0849f7f4: 00000200 00000000 008d00a2 0145381a
>> 0x0849f804: 000000a2 0000008d 2386fce0 00000000
>> 0x0849f814: 04de5d15 00000000 23870238 23870390
>> 0x0849f824: 04d98d4a 0849f7e4 0849fb64 6d0f2eb8
>> 0x0849f834: 00000000 0849f850 04e00192 000001f7
>> 0x0849f844: 0849f85c 0849f858 2386fc70 0849f878
>>
>> /*The last address of the last executed operation...*/
>> Instructions: (pc=0x6d0e75d9)
>> 0x6d0e75c9: 56 8b 0e ff 51 68 85 c0 7d 06 5f 33 c0 5e 59 c3
>> 0x6d0e75d9: 8b 47 04 85 c0 74 15 8b 0d a8 fa 12 6d 8b 16 51
>>
>> /*Most important is sp which is Stack Pointer*/
>> Stack: [0x083a0000,0x084a0000), sp=0x0849f7d4, free space=1021k
>> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
>> code)
>>
>> /*The topmost module indicates  the offending Library..I would check that
>> (awt.dll) version correct AND corresponds with java -version */
>> C [awt.dll+0xe75d9]
>> J sun.awt.windows.WComponentPeer.nativeHandleEvent(Ljava/awt/AWTEvent;)V
>> J sun.awt.windows.WComponentPeer.handleEvent(Ljava/awt/AWTEvent;)V
>> J java.awt.Component.dispatchEventImpl(Ljava/awt/AWTEvent;)V
>> J java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V
>> J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
>> J
>> java.awt.EventDispatchThread.pumpOneEventForHierarchy
>> (ILjava/awt/Component;)Z
>> J
>> java.awt.EventDispatchThread.pumpEventsForHierarchy
>> (ILjava/awt/Conditional;Ljava/awt/Component;)V
>> v ~RuntimeStub::alignment_frame_return Runtime1 stub
>> j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
>> j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
>> j java.awt.EventDispatchThread.run()V+9
>> v ~StubRoutines::call_stub
>> V [jvm.dll+0x8176e]
>> V [jvm.dll+0xd481d]
>> V [jvm.dll+0x8163f]
>> V [jvm.dll+0x8139c]
>> V [jvm.dll+0x9c05c]
>> V [jvm.dll+0xfeece]
>> V [jvm.dll+0xfee9c]
>> C [msvcrt.dll+0x27fb8]
>>
>> /*muck with this at your own peril!*/
>> C [kernel32.dll+0x1d28e]
>>
>> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
>>
>> /*Looks as if a component listener was attempting to handle a
>> native(meaning an OS call) event ..*/
>> /*That 0x00000004 looks suspiciously low..(usually low memory is reserved
>> for System only calls)*/
>> J sun.awt.windows.WComponentPeer.nativeHandleEvent(Ljava/awt/AWTEvent;)siginfo:
>> ExceptionCode=0xc0000005, reading address 0x00000004
>>
>> Most of these errors are resolved by clean install on other words version
>> 1.0 Blah works with version 1.0 BlahBlah
>> but Version 1.1 Blah doesnt work with Version 1.0 BlahBlah
>> As you can imagine debugging these scenarios can get very hairy in a hurry
>> so the more information the better..that said
>> can we see your jvm.cfg ???
>> what version OS are you running?
>> what version Java?
>> what version Tomcat?
>>
>> M-
>> *********************************************************************
>> This email message and any files transmitted with it contain confidential
>> information intended only for the person(s) to whom this email message is
>> addressed.  If you have received this email message in error, please
>> notify
>> the sender immediately by telephone or email and destroy the original
>> message without making a copy.  Thank you.
>>
>>
>>
>> ----- Original Message -----
>> From: "Kim Albee" <mtitania@gmail.com>
>> To: "Tomcat Users List" <users@tomcat.apache.org>; "Martin Gainty" <
>> mgainty@hotmail.com>
>> Sent: Friday, July 21, 2006 11:09 AM
>> Subject: Re: Tomcat Crashing -- how do I read the resulting
>> hs_err_pid11598.log?
>>
>>
>> > Martin --
>> >
>> > How do I tell when the memory allocation happens?  what do I look for in
>> the
>> > logfiles?  I sent the output that was put into the catalina.out file
>> with
>> > the original post -- there is nothing prior to that as far as errors in
>> > processing in the catalina.out file.
>> >
>> > thanks,
>> > Kim :-)
>> >
>> > On 7/20/06, Martin Gainty <mgainty@hotmail.com> wrote:
>> >>
>> >> Good Morning Darryl-
>> >>
>> >> make certain your HW is rock solid
>> >> then I would inquire
>> >> When does the memory allocation happen (e.g. at Tomcat startup. at
>> webapp
>> >> init, when processing big and bulky PDF's)
>> >> check the logs at $TOMCAT_HOME/logs
>> >> If its tomcat crashing (misconfigured server.xml or JVM bug check
>> >> jakarta_service_YYYYMMDD.log)
>> >> If its a genuine error (thrown to stderr) look at stderr_YYYYMMDD.log
>> >> If its webapp specific check the stdout_YYYYMMDD.log AND/OR
>> catalina.out
>> >>
>> >> M-
>> >> *********************************************************************
>> >> This email message and any files transmitted with it contain
>> confidential
>> >> information intended only for the person(s) to whom this email message
>> is
>> >> addressed.  If you have received this email message in error, please
>> >> notify
>> >> the sender immediately by telephone or email and destroy the original
>> >> message without making a copy.  Thank you.
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Darryl Miles" <darryl-mailinglists@netbauds.net>
>> >> To: "Tomcat Users List" <users@tomcat.apache.org>
>> >> Sent: Thursday, July 20, 2006 7:31 AM
>> >> Subject: Re: Tomcat Crashing -- how do I read the resulting
>> >> hs_err_pid11598.log?
>> >>
>> >>
>> >> > Kim Albee wrote:
>> >> >> The box has 4GB of RAM on it, and has experienced a memory
>> failure.  We
>> >> >> tested the physical RAM on the server, and it failed 2 extended
>> memory
>> >> >> tests, so we replaced the RAM.  We also saw that the swap space
was
>> >> only at
>> >> >> 1.5GB, so we upped that to 6.5 GB.
>> >> >
>> >> > For most real-time client serving applications using any swap space
>> to
>> >> > service any part of those requests is counter productive.
>> >> >
>> >> > It only makes sense if you are using the swap as some form of data
>> >> > backing store, but then you have to ask why not just leave it in a
>> file
>> >> > anyway.  The most natural backing store.
>> >> >
>> >> >
>> >> >> so my question is:  how do I read/interpret the hs_err_pid11598.log
>> >> file so
>> >> >> I can figure out what is happening here?
>> >> >
>> >> > First have you found the file ?  Its usualy in the current working
>> >> > directory of the JVM.
>> >> >
>> >> > find / -name "hs_err_pid11598.log" 2>/dev/null
>> >> >
>> >> >
>> >> > Darryl
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To start a new topic, e-mail: users@tomcat.apache.org
>> >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> >> > For additional commands, e-mail: users-help@tomcat.apache.org
>> >> >
>> >> >
>> >
>
Mime
View raw message