You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Chris Kaido <to...@gmail.com> on 2004/11/16 12:54:59 UTC
Understanding origin of "Unexpected exception ... outside the VM"
Hi,
I'm running a JSP application on Apache/Tomcat with mod_jk2 on Solaris
8. The application has more than 6Gb of RAM (yes, read "six") to run
and it crashes irregularly (see error output below) with exactly the
same error. My purpose is to determine where the problem stands ... so
I could look into one ore two components instead of everything at the
same time, thus avoiding wars between programmers and system guys
(like me) :)
Is it in ...
- Tomcat 4.1.30 ?
- Apache 2.0.49 with mod_jk2
- Java VM 1.4.2_04 ?
- the JSP pages itself ?
Are there some exhaustive causes for this kind of error ?
Any thoughts will be appreciated ...
thanks,
Chris.
<snip>
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xFFFFFFFF7EF499A4
Function=[Unknown. Nearest: madvise+0xC0]
Library=/usr/lib/64/libc.so.1
Current Java thread:
at kyudo.NativeCall.Call_C_tpcall(Native Method)
at kyudo.NativeCall.tp_call(NativeCall.java:58)
at kyudo.KyudoDispatcher$ObjectApartment.get_result(KyudoDispatcher.java:345)
at kyudo.KyudoDispatcher$ObjectApartment.run(KyudoDispatcher.java:306)
Dynamic libraries:
0x100000000 /kyudoweb/java/bin/sparcv9/java
0xffffffff7f300000 /usr/lib/64/libthread.so.1
0xffffffff7f500000 /usr/lib/64/libdl.so.1
0xffffffff7ef00000 /usr/lib/64/libc.so.1
0xffffffff7d400000 /kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/server/libjvm.so
0xffffffff7d200000 /usr/lib/64/libCrun.so.1
0xffffffff7cf00000 /usr/lib/64/libsocket.so.1
0xffffffff7cd00000 /usr/lib/64/libnsl.so.1
0xffffffff7cb00000 /usr/lib/64/libm.so.1
0xffffffff7c900000 /usr/lib/64/libsched.so.1
0xffffffff7ed00000 /usr/lib/64/libw.so.1
0xffffffff7c500000 /usr/lib/64/libmp.so.2
0xffffffff7c200000
/kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/native_threads/libhpi.so
0xffffffff7be00000 /kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/libverify.so
0xffffffff7bc00000 /kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/libjava.so
0xffffffff7b900000 /kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/libzip.so
0xfffffffdae800000 /kyudoweb/j2sdk1.4.2_04/jre/lib/sparcv9/libnet.so
0xfffffffdad100000
/kyudoweb/thalerv1.4/webapps/kyudo/nativecall/libnativecall.so
0xfffffffdacf00000 /tuxweb/lib/libwsc.so.71
0xfffffffdacd00000 /tuxweb/lib/libbuft.so.71
0xfffffffdaca00000 /tuxweb/lib/libgpnet.so.71
0xfffffffdac800000 /tuxweb/lib/libfml.so.71
0xfffffffdac600000 /tuxweb/lib/libfml32.so.71
0xfffffffdac300000 /tuxweb/lib/libengine.so.71
0xfffffffdac100000 /usr/lib/64/libpthread.so.1
0xfffffffdabe00000 /usr/lib/64/librt.so.1
0xfffffffdabc00000 /usr/lib/64/libaio.so.1
0xfffffffdab700000 /tuxweb/lib/registry.so
Heap at VM Abort:
Heap
def new generation total 1696320K, used 1485783K
[0xfffffffdb3800000, 0xfffffffe1e2c0000, 0xfffffffe33800000)
eden space 1644928K, 87% used [0xfffffffdb3800000,
0xfffffffe0b0c5de0, 0xfffffffe17e60000)
from space 51392K, 99% used [0xfffffffe17e60000,
0xfffffffe1b08fff8, 0xfffffffe1b090000)
to space 51392K, 0% used [0xfffffffe1b090000,
0xfffffffe1b090000, 0xfffffffe1e2c0000)
tenured generation total 3495296K, used 2381505K
[0xfffffffe33800000, 0xffffffff08d60000, 0xffffffff33800000)
the space 3495296K, 68% used [0xfffffffe33800000,
0xfffffffec4db0560, 0xfffffffec4db0600, 0xffffffff08d60000)
compacting perm gen total 16384K, used 13647K [0xffffffff33800000,
0xffffffff34800000, 0xffffffff37800000)
the space 16384K, 83% used [0xffffffff33800000,
0xffffffff34553f10, 0xffffffff34554000, 0xffffffff34800000)
</snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the
VM"
Posted by Tim Funk <fu...@joedog.org>.
JVM crash means native code doing bad things and since ..
Current Java thread:
at kyudo.NativeCall.Call_C_tpcall(Native Method)
at kyudo.NativeCall.tp_call(NativeCall.java:58)
That looks like a good candidate.
-Tim
Chris Kaido wrote:
> Hi,
>
> I'm running a JSP application on Apache/Tomcat with mod_jk2 on Solaris
> 8. The application has more than 6Gb of RAM (yes, read "six") to run
> and it crashes irregularly (see error output below) with exactly the
> same error. My purpose is to determine where the problem stands ... so
> I could look into one ore two components instead of everything at the
> same time, thus avoiding wars between programmers and system guys
> (like me) :)
>
> Is it in ...
> - Tomcat 4.1.30 ?
> - Apache 2.0.49 with mod_jk2
> - Java VM 1.4.2_04 ?
> - the JSP pages itself ?
>
> Are there some exhaustive causes for this kind of error ?
>
> Any thoughts will be appreciated ...
>
> thanks,
>
> Chris.
>
> <snip>
> An unexpected exception has been detected in native code outside the VM.
> Unexpected Signal : 11 occurred at PC=0xFFFFFFFF7EF499A4
> Function=[Unknown. Nearest: madvise+0xC0]
> Library=/usr/lib/64/libc.so.1
>
> Current Java thread:
> at kyudo.NativeCall.Call_C_tpcall(Native Method)
> at kyudo.NativeCall.tp_call(NativeCall.java:58)
> at kyudo.KyudoDispatcher$ObjectApartment.get_result(KyudoDispatcher.java:345)
> at kyudo.KyudoDispatcher$ObjectApartment.run(KyudoDispatcher.java:306)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the VM"
Posted by "Steven J. Owens" <pu...@darksleep.com>.
On Wed, Nov 17, 2004 at 05:54:58AM -0600, QM wrote:
> On Wed, Nov 17, 2004 at 09:26:32AM +0100, Chris Kaido wrote:
> : I'm running solaris on Sparc hardware.
> : How could I verify the validity of my RAM without ... changing it :) ?
>
> Ehh, this may be a Google. ;) I'm pretty sure there are some Solaris
> memory test tools out there.
>
> As far as testing the memory itself, there's no way (AFAIK) to exercise
> individual chips unless you open the box and shuffle them in/out
> yourself.
>
> If you have a Sun support contract, now's the time to put it to use. ;)
You might find this mailing list and/or its archives useful:
http://isp-lists.isp-planet.com/isp-solaris/
--
Steven J. Owens
puff@darksleep.com
"I'm going to make broad, sweeping generalizations and strong,
declarative statements, because otherwise I'll be here all night and
this document will be four times longer and much less fun to read.
Take it all with a grain of salt." - http://darksleep.com/notablog
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the VM"
Posted by Chris Kaido <to...@gmail.com>.
Thank you for your answers, I now have a research base :)
thx,
Chris.
On Wed, 17 Nov 2004 05:54:58 -0600, QM <qm...@brandxdev.net> wrote:
> On Wed, Nov 17, 2004 at 09:26:32AM +0100, Chris Kaido wrote:
> : I'm running solaris on Sparc hardware.
> : How could I verify the validity of my RAM without ... changing it :) ?
>
> Ehh, this may be a Google. ;) I'm pretty sure there are some Solaris
> memory test tools out there.
>
> As far as testing the memory itself, there's no way (AFAIK) to exercise
> individual chips unless you open the box and shuffle them in/out
> yourself.
>
> If you have a Sun support contract, now's the time to put it to use. ;)
>
>
>
> -QM
>
> --
>
> software -- http://www.brandxdev.net
> tech news -- http://www.RoarNetworX.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the VM"
Posted by QM <qm...@brandxdev.net>.
On Wed, Nov 17, 2004 at 09:26:32AM +0100, Chris Kaido wrote:
: I'm running solaris on Sparc hardware.
: How could I verify the validity of my RAM without ... changing it :) ?
Ehh, this may be a Google. ;) I'm pretty sure there are some Solaris
memory test tools out there.
As far as testing the memory itself, there's no way (AFAIK) to exercise
individual chips unless you open the box and shuffle them in/out
yourself.
If you have a Sun support contract, now's the time to put it to use. ;)
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the VM"
Posted by Chris Kaido <to...@gmail.com>.
First, thank you for your answers.
I'm running solaris on Sparc hardware.
How could I verify the validity of my RAM without ... changing it :) ?
Chris.
On Tue, 16 Nov 2004 06:49:13 -0600, QM <qm...@brandxdev.net> wrote:
> On Tue, Nov 16, 2004 at 12:54:59PM +0100, Chris Kaido wrote:
> : The application has more than 6Gb of RAM (yes, read "six") to run
> : and it crashes irregularly
> : [snip]
> :
> : Is it in ...
> : - Tomcat 4.1.30 ?
> : - Apache 2.0.49 with mod_jk2
> : - Java VM 1.4.2_04 ?
> : - the JSP pages itself ?
>
>
> The error message indicates the crash occurs during a native (JNI) call
> done by your code. That rules out the JSPs, Apache, and Tomcat.
>
> Read on:
>
> : An unexpected exception has been detected in native code outside the VM.
> : Unexpected Signal : 11 occurred at PC=0xFFFFFFFF7EF499A4
> : Function=[Unknown. Nearest: madvise+0xC0]
> : Library=/usr/lib/64/libc.so.1
>
> Let's see... random crashes, "singal 11" errors, and in a system library
> that should be fairly stable... This is likely a hardware problem. You
> don't say whether you're running Solaris Sparc or x86, but sig11 errors
> on the latter are typically indicative of bad RAM.
>
> -QM
>
> --
>
> software -- http://www.brandxdev.net
> tech news -- http://www.RoarNetworX.com
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Understanding origin of "Unexpected exception ... outside the VM"
Posted by QM <qm...@brandxdev.net>.
On Tue, Nov 16, 2004 at 12:54:59PM +0100, Chris Kaido wrote:
: The application has more than 6Gb of RAM (yes, read "six") to run
: and it crashes irregularly
: [snip]
:
: Is it in ...
: - Tomcat 4.1.30 ?
: - Apache 2.0.49 with mod_jk2
: - Java VM 1.4.2_04 ?
: - the JSP pages itself ?
The error message indicates the crash occurs during a native (JNI) call
done by your code. That rules out the JSPs, Apache, and Tomcat.
Read on:
: An unexpected exception has been detected in native code outside the VM.
: Unexpected Signal : 11 occurred at PC=0xFFFFFFFF7EF499A4
: Function=[Unknown. Nearest: madvise+0xC0]
: Library=/usr/lib/64/libc.so.1
Let's see... random crashes, "singal 11" errors, and in a system library
that should be fairly stable... This is likely a hardware problem. You
don't say whether you're running Solaris Sparc or x86, but sig11 errors
on the latter are typically indicative of bad RAM.
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org