- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Java Hotspot crash depends on directory name lengh...
Operating System - HP-UX
1752489
Members
5510
Online
108788
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
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
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
08-20-2004 01:06 AM
08-20-2004 01:06 AM
Java Hotspot crash depends on directory name lenght?
Hallo,
we see a very strange behaviour on HPUX B.11.11 U 9000/800, vpar with Java JDK 1.3.1_13 (same with JDK 1.4.2 or 1.3.1_12).
Starting a small Java program in some directory e.g. /data/test it works, when we rename the directory in /data/testtest, it crashes in mallinfo, the stack is posted below.
whether it crashes or not also seems to depend in which order the classes are loaded (how CLASSPATH is ordered) and whether classes are in .jars or unpacked.
This just happens on one of our six HPUX machines.
Does anyone have an idea what could be wrong with this machine?
Patches are up to date, PHCO_30544 and PHCO_31061 are installed.
----------------
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xC0197B5C
Function name=mallinfo
Library=/usr/lib/libc.2
Current Java thread:
"main" prio=7 tid=0x00031140 nid=1 lwp_id=148442 runnable [0x7b043000..0x7b041650]
at java.lang.ClassLoader.findBootstrapClass(Native Method)
at java.lang.ClassLoader.findBootstrapClass0(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
- locked <0x77407c80> (a sun.misc.Launcher$ExtClassLoader)
at java.lang.ClassLoader.loadClass(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.versant.trans.Wrappers.java_lang_Class_forName(Wrappers.java:88)
at com.versant.trans.TransSession.classForName(TransSession.java:2678)
at com.versant.trans.TransSession.newInstance(TransSession.java:4373)
at com.versant.trans.TransSession.generatePickler(TransSession.java:3301)
at com.versant.trans.TransSession.generatePickler(TransSession.java:3292)
at com.versant.trans.TransSession.findPicklerForClassHandle(TransSession.java:3164)
at com.versant.trans.TransSession.findClassHandle(TransSession.java:3086)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at com.versant.trans.TransSession.makePersistent(TransSession.java:4024)
at com.versant.trans.TransSession.makePersistent(TransSession.java:1529)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at com.versant.trans.TransSession.makePersistent(TransSession.java:1510)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at Test.main(Test.java:11)
Dynamic libraries:
/opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/java
text:0x00001000-0x000073ac data:0x00008000-0x000086b8
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl
text:0xc3400000-0xc3cb0000 data:0x7af52000-0x7b01b000
/usr/lib/libm.2
text:0xc0080000-0xc00ac000 data:0x7af1a000-0x7af1b000
/usr/lib/librt.2
text:0xc1138000-0xc113c000 data:0x7af1b000-0x7af1c000
/usr/lib/libcl.2
text:0xc03c0000-0xc04ab000 data:0x7af1d000-0x7af29000
/usr/lib/libisamstub.1
text:0xc005f000-0xc0060000 data:0x7af1c000-0x7af1d000
/usr/lib/libCsup.2
text:0xc0310000-0xc032b000 data:0x7af29000-0x7af2c000
/usr/lib/libpthread.1
text:0xc0040000-0xc0059000 data:0x7b01b000-0x7b01e000
/usr/lib/libc.2
text:0xc0100000-0xc0246000 data:0x7b023000-0x7b036000
/usr/lib/libdld.2
text:0xc0004000-0xc0007000 data:0x7b01e000-0x7b01f000
/opt/java1.3/jre/lib/PA_RISC2.0/native_threads/libhpi.sl
text:0xc18e0000-0xc18f2000 data:0x7af12000-0x7af14000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libverify.sl
text:0xc1c60000-0xc1c70000 data:0x7af00000-0x7af01000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libjava.sl
text:0xc1fa0000-0xc1fcd000 data:0x7aefb000-0x7af00000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libzip.sl
text:0xc1ce0000-0xc1cf3000 data:0x7aef9000-0x7aefb000
/opt/versant/vds605/lib/libjvi6.0.5.sl
text:0xc4d00000-0xc4f2c000 data:0x789ac000-0x789ff000
/usr/lib/libnss_files.1
text:0xc0034000-0xc003d000 data:0x7ac41000-0x7ac42000
Local Time = Fri Aug 20 14:56:56 2004
Elapsed Time = 0
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Server VM (1.3.1 1.3.1.13-_10_feb_2004_17_15 PA2.0 mixed mode)
#
# An error report file has been saved as /var/tmp/hs_err_pid8527.log.
# Please refer to the file for further information.
#
Abort
we see a very strange behaviour on HPUX B.11.11 U 9000/800, vpar with Java JDK 1.3.1_13 (same with JDK 1.4.2 or 1.3.1_12).
Starting a small Java program in some directory e.g. /data/test it works, when we rename the directory in /data/testtest, it crashes in mallinfo, the stack is posted below.
whether it crashes or not also seems to depend in which order the classes are loaded (how CLASSPATH is ordered) and whether classes are in .jars or unpacked.
This just happens on one of our six HPUX machines.
Does anyone have an idea what could be wrong with this machine?
Patches are up to date, PHCO_30544 and PHCO_31061 are installed.
----------------
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0xC0197B5C
Function name=mallinfo
Library=/usr/lib/libc.2
Current Java thread:
"main" prio=7 tid=0x00031140 nid=1 lwp_id=148442 runnable [0x7b043000..0x7b041650]
at java.lang.ClassLoader.findBootstrapClass(Native Method)
at java.lang.ClassLoader.findBootstrapClass0(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
- locked <0x77407c80> (a sun.misc.Launcher$ExtClassLoader)
at java.lang.ClassLoader.loadClass(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
- locked <0x77410ba8> (a sun.misc.Launcher$AppClassLoader)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.versant.trans.Wrappers.java_lang_Class_forName(Wrappers.java:88)
at com.versant.trans.TransSession.classForName(TransSession.java:2678)
at com.versant.trans.TransSession.newInstance(TransSession.java:4373)
at com.versant.trans.TransSession.generatePickler(TransSession.java:3301)
at com.versant.trans.TransSession.generatePickler(TransSession.java:3292)
at com.versant.trans.TransSession.findPicklerForClassHandle(TransSession.java:3164)
at com.versant.trans.TransSession.findClassHandle(TransSession.java:3086)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at com.versant.trans.TransSession.makePersistent(TransSession.java:4024)
at com.versant.trans.TransSession.makePersistent(TransSession.java:1529)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at com.versant.trans.TransSession.makePersistent(TransSession.java:1510)
- locked <0x774ba608> (a com.versant.trans.TransSession)
at Test.main(Test.java:11)
Dynamic libraries:
/opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/java
text:0x00001000-0x000073ac data:0x00008000-0x000086b8
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl
text:0xc3400000-0xc3cb0000 data:0x7af52000-0x7b01b000
/usr/lib/libm.2
text:0xc0080000-0xc00ac000 data:0x7af1a000-0x7af1b000
/usr/lib/librt.2
text:0xc1138000-0xc113c000 data:0x7af1b000-0x7af1c000
/usr/lib/libcl.2
text:0xc03c0000-0xc04ab000 data:0x7af1d000-0x7af29000
/usr/lib/libisamstub.1
text:0xc005f000-0xc0060000 data:0x7af1c000-0x7af1d000
/usr/lib/libCsup.2
text:0xc0310000-0xc032b000 data:0x7af29000-0x7af2c000
/usr/lib/libpthread.1
text:0xc0040000-0xc0059000 data:0x7b01b000-0x7b01e000
/usr/lib/libc.2
text:0xc0100000-0xc0246000 data:0x7b023000-0x7b036000
/usr/lib/libdld.2
text:0xc0004000-0xc0007000 data:0x7b01e000-0x7b01f000
/opt/java1.3/jre/lib/PA_RISC2.0/native_threads/libhpi.sl
text:0xc18e0000-0xc18f2000 data:0x7af12000-0x7af14000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libverify.sl
text:0xc1c60000-0xc1c70000 data:0x7af00000-0x7af01000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libjava.sl
text:0xc1fa0000-0xc1fcd000 data:0x7aefb000-0x7af00000
/opt/java1.3/bin/../jre/lib/PA_RISC2.0/libzip.sl
text:0xc1ce0000-0xc1cf3000 data:0x7aef9000-0x7aefb000
/opt/versant/vds605/lib/libjvi6.0.5.sl
text:0xc4d00000-0xc4f2c000 data:0x789ac000-0x789ff000
/usr/lib/libnss_files.1
text:0xc0034000-0xc003d000 data:0x7ac41000-0x7ac42000
Local Time = Fri Aug 20 14:56:56 2004
Elapsed Time = 0
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Server VM (1.3.1 1.3.1.13-_10_feb_2004_17_15 PA2.0 mixed mode)
#
# An error report file has been saved as /var/tmp/hs_err_pid8527.log.
# Please refer to the file for further information.
#
Abort
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2004 01:28 AM
08-20-2004 01:28 AM
Re: Java Hotspot crash depends on directory name lenght?
Hi
Since it is only 1 machine and there are I asume no real differences between the boxes then I suggest Hardware
Last time I saw such a thing it was a
BAD FloatingPointCo-processor
Steve Steel
Since it is only 1 machine and there are I asume no real differences between the boxes then I suggest Hardware
Last time I saw such a thing it was a
BAD FloatingPointCo-processor
Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
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