hpux JVM crashes consistently

[Wayne Xin]

Not sure if this is the right board for Java. Please point me to the right one if not. I'm using hpux's java1.3 that comes with Weblogic. The JVM crashed with the following error output:

#
# Java version:
# Java HotSpot(TM) Server VM (mixed mode)
#
# HotSpot Virtual Machine Error, Internal Error
#
# Fatal: null exception in compiled code
#
# Error ID: /CLO/Components/JAVA_HOTSPOT/Src/build/hp-ux/../../src/share/vm/runt
ime/sharedRuntime.cpp, 389
#
# Problematic Thread: prio=2 tid=0x01a4e1c0 nid=174 lwp_id=1424 runnable
#

[Helen French]

Hi,

Did you apply the latest Java patches ? Get it download from here, that may solve the issue:

http://www.hp.com/products1/unix/java/index.html

HTH,
Shiju

[Olav Baadsvik]

Hi,

This can be any kind of problem.
You can start by seeing if you get
the same problem when you run java
with the option -classic.
This will replace the HotSpot compiler with
the Just-In_Time (JIT) compiler

Regards
Olav

[Wayne Xin]

NOt sure if HP JVM developers come to this board. Anyway, the JVM still crashes consistently on a reflection method call even with -classic option. It doesn't happen the first time it makes the reflection call. This reflection call may be running in a multi-threaded environment.

I don't know if I can write a small program to reproduce the problem. But my JVM crashes every single time I run the task.

BTW, I've installed all the required patches.
BTW, the same application runs on Solaris just fine.

[Jeff Schussele]

Could be the version that BEA delivered w/WebLogic is causing the problems.
Why don't you try a version direct from HP - here's the URL for all the current 1.3 vers (includes patch info, SDKs, RTEs, 1.3.0.1 & 1.3.0.2):

http://www.hp.com/products1/unix/java/java2/sdkrte1_3/downloads/index.html

HTH,
Jeff

[Jeff Schussele]

Could be the version that BEA delivered w/WebLogic is causing the problems.
Why don't you try a version direct from HP - here's the URL for all the current 1.3 vers (includes patch info, SDKs, RTEs, 1.3.1.01 & 1.3.1.02):

http://www.hp.com/products1/unix/java/java2/sdkrte1_3/downloads/index.html

HTH,
Jeff

[Wayne Xin]

Now I consistently get the following before the Java Hotspot message (starting with "#", see the 1st post). Can anybody guess what went wrong? When this happened, in my code, I just "new"ed a CocoProxyM class (Cocobase thing) and is trying to call setPropObjectData() which sets a java.util.Properties object.

Stack_Trace: error while unwinding stack
( 0) 0xc2fd8474 report_error__FbPCciN22e + 0x5c [/creekpath/AIMserver/jdk1
31/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1) 0xc2fd8124 report_fatal__FPCciT1e + 0x6c [/creekpath/AIMserver/jdk131
/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2) 0xc3112b08 compute_exception_return_address__13SharedRuntimeSFl + 0x19
0 [/creekpath/AIMserver/jdk131/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]

[P.Durga Prasad Babu]

Did you get any solution for this problem.

I am having similar problems while deploying the applications on Sun ONE Application Server 7(We have ported it to HP-Unix).

[Ramesh Anand]

Hi
I am also facing the same problem.If you find any solution, please let me know.

I got the following error:
Stack_Trace: error while unwinding stack
( 0) 0xc27d9454 report_error__FbPCciN22e + 0x5c [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1) 0xc27d9104 report_fatal__FPCciT1e + 0x6c [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2) 0xc2916bbc shl_getsymbols_all__10shlib_hpuxSFsiPP10shl_symbolPPP10shl_symbolPPiPi + 0x164 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 3) 0xc29171e0 pc2shsym__10shlib_hpuxSFPUcPcUi + 0x200 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 4) 0xc28f12d4 dll_address_to_function_name__2osSFPUc + 0x24 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 5) 0xc28eda68 handle_unexpected_exception__2osSFP6ThreadiPUcPv + 0x420 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 6) 0xc28f7158 JVM_handle_hpux_signal__Q2_2os4HpuxSFiP9__siginfoPvT1 + 0x718 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 7) 0xc28f40c4 signalHandler__Q2_2os4HpuxSFiP9__siginfoPv + 0x14 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 8) 0xc01f1528 _sigreturn [/usr/lib/libc.2]
( 9) 0xc0158a38 __memset20 + 0xb8 [/usr/lib/libc.2]
[error occured during error reporting]
Stack_Trace: error while unwinding stack
( 0) 0xc27d9454 report_error__FbPCciN22e + 0x5c [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1) 0xc27d9104 report_fatal__FPCciT1e + 0x6c [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2) 0xc2916bbc shl_getsymbols_all__10shlib_hpuxSFsiPP10shl_symbolPPP10shl_symbolPPiPi + 0x164 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 3) 0xc29171e0 pc2shsym__10shlib_hpuxSFPUcPcUi + 0x200 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 4) 0xc28f12d4 dll_address_to_function_name__2osSFPUc + 0x24 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 5) 0xc28eda68 handle_unexpected_exception__2osSFP6ThreadiPUcPv + 0x420 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 6) 0xc28f7158 JVM_handle_hpux_signal__Q2_2os4HpuxSFiP9__siginfoPvT1 + 0x718 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 7) 0xc28f40c4 signalHandler__Q2_2os4HpuxSFiP9__siginfoPv + 0x14 [/apps_serv/weblogic/bea/jdk131_03/bin/../jre/lib/PA_RISC2.0/server/libjvm.sl]
( 8) 0xc01f1528 _sigreturn [/usr/lib/libc.2]
( 9) 0xc0158a38 __memset20 + 0xb8 [/usr/lib/libc.2]

[Steven E. Protter]

HP JVM developers if such an animal even exists don't come to this board. The purpose of forums is to fix problems and assist you in that.

There are links on the main http://itrc.hp.com site that let you report and track buhgs.

They are going to need more information to diagnose.

From reading the thread, it could be JVM crashing, it could be the application causing JVM to crash.

It is imperitive that you have installed and in a configured state each and every recommended java patch for your java versions in the link provided to you above.

SEP

[Paddy_1]

can you enable a thread dump and share it.
that way there is a standard way to trace back the root of the problem.