AppletTalk.com Forum Index AppletTalk.com
Java discussions newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Remote dubugging JBoss under 1.5.0 GA causes VM exit...

 
Post new topic   Reply to topic    AppletTalk.com Forum Index -> ibm.software.java.linux
View previous topic :: View next topic  
Author Message
javahollic
Guest





PostPosted: Fri Dec 02, 2005 9:46 pm    Post subject: Remote dubugging JBoss under 1.5.0 GA causes VM exit... Reply with quote



Hi,
Im trying to debug a web application under IBM 1.5.0GA and Jboss
4.0.3SP1, using Socket debugging from Eclipse 3.1.1 to jboss. When I
poke the webapp with a browser, it starts working then the IBM VM
running JBoss dies. Ive tried explicitly turning on the JIT with -Xj9 I
found mentioned on google to no avail. Its totally repeatable. If it
was a problem in the code Id expect a standard java stack not a VM exit,
anyone got clues? Anywhere that I post the full dump to?

Cheers,
andy

------------------------
Console dump as follows:
------------------------
Unhandled exception
Type=Segmentation error vmState=0x00000000
Target=2_30_20051027_03723_LHdSMr (Linux 2.6.12-10-amd64-kCool
CPU=amd64 (1 logical CPUs) (0x4e1d2000 RAM)
J9Generic_Signal_Number=00000004 Signal_Number=0000000b
Error_Value=00000000 Signal_Code=00000001
Handler1=00002AAAAB6158B0 Handler2=00002AAAAB8624B0
InaccessibleAddress=FFFFFFFFFFFFF1D2
RDI=0000000000000001 RSI=000000000000054C RAX=0000000000000000
RBX=00000000040FECC0
RCX=0000000000000001 RDX=FFFFFFFFFFFFF1D2 R8=0000000000000000
R9=00000000032FB53A
R10=0000000043907437 R11=0000000000000001 R12=0000000000000478
R13=00000000040FD488
R14=000000000055A3C8 R15=00000000040FD494
RIP=00002AAAAC5F07CE GS=0005000000000000 FS=0000000500000000
RSP=00000000401A1AD0
EFlags=0000000000010203 CS=000000000000AC34 RBP=00000000040FE84C
ERR=0000000000000005
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=FFFFFFFFFFFFF1D2
xmm0 000000000054b800 (f: 5552128.000000, d: 2.743116e-317)
xmm1 00002aaaab73de40 (f: 2876497408.000000, d: 2.317786e-310)
xmm2 00002aaaab2400c0 (f: 2871263488.000000, d: 2.317786e-310)
xmm3 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm4 00002aaaab73f580 (f: 2876503552.000000, d: 2.317786e-310)
xmm5 00002aaaab2400c0 (f: 2871263488.000000, d: 2.317786e-310)
xmm6 00000000006947a8 (f: 6899624.000000, d: 3.408867e-317)
xmm7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/local/java/ibm150/bin/../jre/bin/libj9jvmti23.so
Module_base_address=00002AAAAC5E4000
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/core.20051202.162007.18614.dmp'
JVMDUMP010I System Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/core.20051202.162007.18614.dmp
JVMDUMP007I JVM Requesting Snap Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/Snap0001.20051202.162007.18614.trc'
JVMDUMP010I Snap Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/Snap0001.20051202.162007.18614.trc
JVMDUMP007I JVM Requesting Java Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/javacore.20051202.162007.18614.txt'
JVMDUMP010I Java Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/javacore.20051202.162007.18614.txt
JVMDUMP013I Processed Dump Event "gpf", detail "".
Back to top
SaketR
Guest





PostPosted: Fri Dec 02, 2005 9:59 pm    Post subject: Re: Remote dubugging JBoss under 1.5.0 GA causes VM exit... Reply with quote



Hi Andy,

-Xj9 does not turn off the JIT. It had some meaning prior to 5.0 GA, but it
is no longer applicable in 5.0.

Try the following command line options and see if it works:

1. -Xint
2. -Xtrace:none
3. -Xint -Xtrace:none

cheers!
SaketR

"javahollic" <javahollic (AT) gmail (DOT) com> wrote in message
news:dmptjm$45ck$1 (AT) news (DOT) boulder.ibm.com...
Quote:
Hi,
Im trying to debug a web application under IBM 1.5.0GA and Jboss 4.0.3SP1,
using Socket debugging from Eclipse 3.1.1 to jboss. When I poke the
webapp with a browser, it starts working then the IBM VM running JBoss
dies. Ive tried explicitly turning on the JIT with -Xj9 I found mentioned
on google to no avail. Its totally repeatable. If it was a problem in
the code Id expect a standard java stack not a VM exit,
anyone got clues? Anywhere that I post the full dump to?

Cheers,
andy
Back to top
cnbailey
Guest





PostPosted: Wed Dec 07, 2005 10:56 pm    Post subject: Re: Remote dubugging JBoss under 1.5.0 GA causes VM exit... Reply with quote



javahollic wrote:
Quote:
Hi,
Im trying to debug a web application under IBM 1.5.0GA and Jboss
4.0.3SP1, using Socket debugging from Eclipse 3.1.1 to jboss. When I
poke the webapp with a browser, it starts working then the IBM VM
running JBoss dies. Ive tried explicitly turning on the JIT with -Xj9 I
found mentioned on google to no avail. Its totally repeatable. If it
was a problem in the code Id expect a standard java stack not a VM exit,
anyone got clues? Anywhere that I post the full dump to?

Cheers,
andy

------------------------
Console dump as follows:
------------------------
Unhandled exception
Type=Segmentation error vmState=0x00000000
Target=2_30_20051027_03723_LHdSMr (Linux 2.6.12-10-amd64-kCool
CPU=amd64 (1 logical CPUs) (0x4e1d2000 RAM)
J9Generic_Signal_Number=00000004 Signal_Number=0000000b
Error_Value=00000000 Signal_Code=00000001
Handler1=00002AAAAB6158B0 Handler2=00002AAAAB8624B0
InaccessibleAddress=FFFFFFFFFFFFF1D2
RDI=0000000000000001 RSI=000000000000054C RAX=0000000000000000
RBX=00000000040FECC0
RCX=0000000000000001 RDX=FFFFFFFFFFFFF1D2 R8=0000000000000000
R9=00000000032FB53A
R10=0000000043907437 R11=0000000000000001 R12=0000000000000478
R13=00000000040FD488
R14=000000000055A3C8 R15=00000000040FD494
RIP=00002AAAAC5F07CE GS=0005000000000000 FS=0000000500000000
RSP=00000000401A1AD0
EFlags=0000000000010203 CS=000000000000AC34 RBP=00000000040FE84C
ERR=0000000000000005
TRAPNO=000000000000000E OLDMASK=0000000000000000 CR2=FFFFFFFFFFFFF1D2
xmm0 000000000054b800 (f: 5552128.000000, d: 2.743116e-317)
xmm1 00002aaaab73de40 (f: 2876497408.000000, d: 2.317786e-310)
xmm2 00002aaaab2400c0 (f: 2871263488.000000, d: 2.317786e-310)
xmm3 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm4 00002aaaab73f580 (f: 2876503552.000000, d: 2.317786e-310)
xmm5 00002aaaab2400c0 (f: 2871263488.000000, d: 2.317786e-310)
xmm6 00000000006947a8 (f: 6899624.000000, d: 3.408867e-317)
xmm7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
xmm15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/local/java/ibm150/bin/../jre/bin/libj9jvmti23.so
Module_base_address=00002AAAAC5E4000
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/core.20051202.162007.18614.dmp'
JVMDUMP010I System Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/core.20051202.162007.18614.dmp
JVMDUMP007I JVM Requesting Snap Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/Snap0001.20051202.162007.18614.trc'
JVMDUMP010I Snap Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/Snap0001.20051202.162007.18614.trc
JVMDUMP007I JVM Requesting Java Dump using
'/usr/local/apps/jboss-4.0.3SP1/bin/javacore.20051202.162007.18614.txt'
JVMDUMP010I Java Dump written to
/usr/local/apps/jboss-4.0.3SP1/bin/javacore.20051202.162007.18614.txt
JVMDUMP013I Processed Dump Event "gpf", detail "".

This is a failure in JVMTI:
Module=/usr/local/java/ibm150/bin/../jre/bin/libj9jvmti23.so
so is most likely a JVM bug.

If you can run gdb against the core.dmp file to generate the stack trace
then it may make it clearer as to what the real problem is.

Chris
Back to top
Display posts from previous:   
Post new topic   Reply to topic    AppletTalk.com Forum Index -> ibm.software.java.linux All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.