- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: JVM Crash issue: Compiler thread crashed while...
Operating System - Linux
1748109
Members
4850
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2006 06:42 PM
тАО01-04-2006 06:42 PM
JVM Crash issue: Compiler thread crashed while compiling a method
Hello,
We are getting the following problem from the JVM. The JVM crashes following this problem.
Excerpt from application log:
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Error 0
si_code [1]: SEGV_MAPERR [addr: 0x1e1e1e10]
Aborting...
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x1E1E1E10
Function=[Unknown.]
Compiler thread crashed while compiling a method!
Compiled method class=java.lang.System
Compiled method name=currentTimeMillis
Compiled method signature=()J
Library=(N/A)
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:
"CompilerThread1" daemon prio=8 tid=0006c300 nid=10 lwp_id=511444 runnable [0x00000000..0x69c00158]
Dynamic libraries:
/opt/java1.4/bin/IA64N/java
text:0x00001000-0x00024aa0 data:0x00025000-0x000271a8
/usr/lib/hpux32/libpthread.so.1
text:0xc008d000-0xc011fcb0 data:0x777ef000-0x777f1508
/opt/java1.4/jre/lib/IA64N/server/libjvm.so
text:0xc80c9000-0xc8dd7c90 data:0x77500000-0x776fba08
/usr/lib/hpux32/libdl.so.1
text:0xc039f000-0xc03a1660 data:0x777ec000-0x777ec068
/usr/lib/hpux32/libc.so.1
text:0xc0120000-0xc039e300 data:0x777d0000-0x777e10f8
/usr/lib/hpux32/libm.so.1
text:0xc050a000-0xc066fba0 data:0x777e9000-0x777e95d8
/usr/lib/hpux32/librt.so.1
text:0xc340d000-0xc34131f0 data:0x777e6000-0x777e61a8
/usr/lib/hpux32/libuca.so.1
text:0xc0d44000-0xc0d4baf0 data:0x777e5000-0x777e5150
/usr/lib/hpux32/libunwind.so.1
text:0xc0cfd000-0xc0d43470 data:0x777ce000-0x777cf1f0
/usr/lib/hpux32/libcl.so.1
text:0xc3178000-0xc3178304 data:0x777e2000-0x777e2018
/usr/lib/hpux32/libCsup.so.1
text:0xc0cb5000-0xc0cfc0f0 data:0x777c7000-0x777cdbe8
/usr/lib/hpux32/libIO77.so.1
text:0xc3221000-0xc32bd410 data:0x777b8000-0x777c2918
/opt/java1.4/jre/lib/IA64N/native_threads/libhpi.so
text:0xc51e5000-0xc5208440 data:0x777ae000-0x777af880
/opt/java1.4/jre/lib/IA64N/libverify.so
text:0xc5209000-0xc5227a10 data:0x777aa000-0x777ab0a8
/opt/java1.4/jre/lib/IA64N/libjava.so
text:0xc5228000-0xc526e530 data:0x777a8000-0x777a95d0
/opt/java1.4/jre/lib/IA64N/libzip.so
text:0xc526f000-0xc529d250 data:0x777a4000-0x777a5870
/opt/java1.4/jre/lib/IA64N/libnet.so
text:0xc5af3000-0xc5b16820 data:0x777a1000-0x777a16d8
/usr/lib/hpux32/libnm.so
text:0xc0d4c000-0xc0d6b3a0 data:0x777a0000-0x777a0458
Heap at VM Abort:
Heap
def new generation total 5632K, used 2146K [6b400000, 6ba10000, 6c950000)
eden space 5056K, 42% used [6b400000, 6b618598, 6b8f0000)
from space 576K, 0% used [6b980000, 6b9804e8, 6ba10000)
to space 576K, 0% used [6b8f0000, 6b8f0000, 6b980000)
tenured generation total 12480K, used 2925K [6c950000, 6d580000, 6f400000)
the space 12480K, 23% used [6c950000, 6cc2b678, 6cc2b800, 6d580000)
compacting perm gen total 16384K, used 3257K [6f400000, 70400000, 73400000)
the space 16384K, 19% used [6f400000, 6f72e5c0, 6f72e600, 70400000)
Local Time = Thu Dec 29 16:21:45 2005
Elapsed Time = 21170
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2 1.4.2.07-050121-21:06-IA64N IA64 mixed mode)
#
# An error report file has been saved as hs_err_pid6366.log.
# Please refer to the file for further information.
#
Unhandled signal occurred at 0x1e1e1e1e1e1e1e10
There is some additional information available about the system set-up.
# what `which java`
/opt/java1.4/bin/java:
$Revision: 92453-07 linker linker crt0.o B.11.37 040218 $
HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O ILP32) $Revision: 75.04
$
1.4.2.07-050121-17:14-PA_RISC1.1 (java) Built: 05/01/21-17:18 View: jint
eg_h1.4.2.07.rc3b1
# java -version
java version "1.4.2.07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.07-050121-15:53)
Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.07-050121-21:06-IA64N IA64, mixed
mode)
# uname -a
HP-UX B.11.23 U ia64 2612861475 unlimited-user license
[Removed the hostname for "confidentiality"]
Isn't it strange that Java system call is crashing while compiling? Does any one know the real reason behind this? Could it be related to the system set-up? We already are aware of certain workaround from other posts. But, we would like to know the actual reason behind such problems.
Thanks in advance
Indranil
We are getting the following problem from the JVM. The JVM crashes following this problem.
Excerpt from application log:
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Error 0
si_code [1]: SEGV_MAPERR [addr: 0x1e1e1e10]
Aborting...
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x1E1E1E10
Function=[Unknown.]
Compiler thread crashed while compiling a method!
Compiled method class=java.lang.System
Compiled method name=currentTimeMillis
Compiled method signature=()J
Library=(N/A)
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:
"CompilerThread1" daemon prio=8 tid=0006c300 nid=10 lwp_id=511444 runnable [0x00000000..0x69c00158]
Dynamic libraries:
/opt/java1.4/bin/IA64N/java
text:0x00001000-0x00024aa0 data:0x00025000-0x000271a8
/usr/lib/hpux32/libpthread.so.1
text:0xc008d000-0xc011fcb0 data:0x777ef000-0x777f1508
/opt/java1.4/jre/lib/IA64N/server/libjvm.so
text:0xc80c9000-0xc8dd7c90 data:0x77500000-0x776fba08
/usr/lib/hpux32/libdl.so.1
text:0xc039f000-0xc03a1660 data:0x777ec000-0x777ec068
/usr/lib/hpux32/libc.so.1
text:0xc0120000-0xc039e300 data:0x777d0000-0x777e10f8
/usr/lib/hpux32/libm.so.1
text:0xc050a000-0xc066fba0 data:0x777e9000-0x777e95d8
/usr/lib/hpux32/librt.so.1
text:0xc340d000-0xc34131f0 data:0x777e6000-0x777e61a8
/usr/lib/hpux32/libuca.so.1
text:0xc0d44000-0xc0d4baf0 data:0x777e5000-0x777e5150
/usr/lib/hpux32/libunwind.so.1
text:0xc0cfd000-0xc0d43470 data:0x777ce000-0x777cf1f0
/usr/lib/hpux32/libcl.so.1
text:0xc3178000-0xc3178304 data:0x777e2000-0x777e2018
/usr/lib/hpux32/libCsup.so.1
text:0xc0cb5000-0xc0cfc0f0 data:0x777c7000-0x777cdbe8
/usr/lib/hpux32/libIO77.so.1
text:0xc3221000-0xc32bd410 data:0x777b8000-0x777c2918
/opt/java1.4/jre/lib/IA64N/native_threads/libhpi.so
text:0xc51e5000-0xc5208440 data:0x777ae000-0x777af880
/opt/java1.4/jre/lib/IA64N/libverify.so
text:0xc5209000-0xc5227a10 data:0x777aa000-0x777ab0a8
/opt/java1.4/jre/lib/IA64N/libjava.so
text:0xc5228000-0xc526e530 data:0x777a8000-0x777a95d0
/opt/java1.4/jre/lib/IA64N/libzip.so
text:0xc526f000-0xc529d250 data:0x777a4000-0x777a5870
/opt/java1.4/jre/lib/IA64N/libnet.so
text:0xc5af3000-0xc5b16820 data:0x777a1000-0x777a16d8
/usr/lib/hpux32/libnm.so
text:0xc0d4c000-0xc0d6b3a0 data:0x777a0000-0x777a0458
Heap at VM Abort:
Heap
def new generation total 5632K, used 2146K [6b400000, 6ba10000, 6c950000)
eden space 5056K, 42% used [6b400000, 6b618598, 6b8f0000)
from space 576K, 0% used [6b980000, 6b9804e8, 6ba10000)
to space 576K, 0% used [6b8f0000, 6b8f0000, 6b980000)
tenured generation total 12480K, used 2925K [6c950000, 6d580000, 6f400000)
the space 12480K, 23% used [6c950000, 6cc2b678, 6cc2b800, 6d580000)
compacting perm gen total 16384K, used 3257K [6f400000, 70400000, 73400000)
the space 16384K, 19% used [6f400000, 6f72e5c0, 6f72e600, 70400000)
Local Time = Thu Dec 29 16:21:45 2005
Elapsed Time = 21170
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2 1.4.2.07-050121-21:06-IA64N IA64 mixed mode)
#
# An error report file has been saved as hs_err_pid6366.log.
# Please refer to the file for further information.
#
Unhandled signal occurred at 0x1e1e1e1e1e1e1e10
There is some additional information available about the system set-up.
# what `which java`
/opt/java1.4/bin/java:
$Revision: 92453-07 linker linker crt0.o B.11.37 040218 $
HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O ILP32) $Revision: 75.04
$
1.4.2.07-050121-17:14-PA_RISC1.1 (java) Built: 05/01/21-17:18 View: jint
eg_h1.4.2.07.rc3b1
# java -version
java version "1.4.2.07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.07-050121-15:53)
Java HotSpot(TM) Server VM (build 1.4.2 1.4.2.07-050121-21:06-IA64N IA64, mixed
mode)
# uname -a
HP-UX B.11.23 U ia64 2612861475 unlimited-user license
[Removed the hostname for "confidentiality"]
Isn't it strange that Java system call is crashing while compiling? Does any one know the real reason behind this? Could it be related to the system set-up? We already are aware of certain workaround from other posts. But, we would like to know the actual reason behind such problems.
Thanks in advance
Indranil
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2006 06:21 AM
тАО01-06-2006 06:21 AM
Re: JVM Crash issue: Compiler thread crashed while compiling a method
Kind Attn: Indranil,
We were notified this crash situation.
I read your problem report. We will need some more information inorder to provide some meaningful help.
1. Are you able to reproduce this Crash
situation or it is just a timing thing.
2. Normally in a crash-situation like this,
a core file is generated.
Can we have access to the generated
core file.
Any information, will be helpful.
What woraround are you using to get this around.
Regards,
Awais
We were notified this crash situation.
I read your problem report. We will need some more information inorder to provide some meaningful help.
1. Are you able to reproduce this Crash
situation or it is just a timing thing.
2. Normally in a crash-situation like this,
a core file is generated.
Can we have access to the generated
core file.
Any information, will be helpful.
What woraround are you using to get this around.
Regards,
Awais
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2006 02:36 PM
тАО01-08-2006 02:36 PM
Re: JVM Crash issue: Compiler thread crashed while compiling a method
Hello Mr. Awais,
Unfortunately, the scenario is not reproducible. Therefore, we did not need a workaroung.
Also, we got one more core file from another JVM crash, which had over-written the previous core file. Therefore, core from the original problem is not available.
I have sent you the newly generated core file and hs_err file that were generated because of another JVM crash in a separate e-mail. This scenario may be different from the original problem that was reported.
If the original problem is reproduced, we shall retain the core file and send to you for a look.
Thanks
Indranil
Unfortunately, the scenario is not reproducible. Therefore, we did not need a workaroung.
Also, we got one more core file from another JVM crash, which had over-written the previous core file. Therefore, core from the original problem is not available.
I have sent you the newly generated core file and hs_err file that were generated because of another JVM crash in a separate e-mail. This scenario may be different from the original problem that was reported.
If the original problem is reproduced, we shall retain the core file and send to you for a look.
Thanks
Indranil
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP