HPUX 11.00 running java 1.3.1 with weblogic 6.1.

I'm new with Cocobase. Another engineer worked with it and had a CocoDeploy.jar in our APP.ear. My weblogic JVM crashed on the setPropObjectData() of CocoProxyM every single time. It doesn't on Solaris, so I won't say it's totally Cocobase's fault.

I've downloaded the trial version of 4.0 and would like to replace CocoProxyM with the new one. But I'd like to find out if other classes need to be replaced to make this new CocoProxyM work. Also, please let me know if CocoProxyM has changed at all from 3.x version.

The following is what gets printed out when calling setPropObjectData().
--------------------------------------------------------
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]

#
# 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
#

That's a JVM error, why don't you disable the JIT and see
if everything runs? Most likely the HotSpot edition you
are running has some memory bug in it...

The reason we know is CocoBase is pure java, so if you're
getting this crash it's guaranteed to be a JVM bug and not
a CocoBase bug. A pure java call shouldn't be able to crash
a JVM...

THOUGHT Support