topic Re: jre core dumps after install in Operating System - HP-UX

jre core dumps after install

Tom Reppert — Mon, 19 Jul 2004 12:57:16 GMT

Just installed java 1.4.2 (jre) using the HP package on two HP9000 systems(one a K370B, one a K380) both running HPUX 11.0. I have verified that I have installed the patches needed by the jre(PHCO_29959 and its dependencies). /opt/java1.4/jre/bin/java runs fine on the K370B but core dumps with the following error on the K380:

/usr/lib/dld.sl: Call to mmap() failed - TEXT /opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
/usr/lib/dld.sl: Not enough space
Abort(coredump)

I have compared both systems kernel parameters and don't see any values on the K380 below those on the K370B. Also, both systems have exactly the same amount of CPU/RAM.

I have truss'd the java command on both and have examined the core dump but still don't see what I need to change to get past this issue.

Any help is greatly appreciated.

Thanks,

Tom

Re: jre core dumps after install

Steven E. Protter — Mon, 19 Jul 2004 13:06:19 GMT

This is either a problem with the application using java or missing requierd java patches.

http://www.hp.com/go/java for the patches. Make sure they're all in.

SEP

Re: jre core dumps after install

Tom Reppert — Tue, 20 Jul 2004 15:49:26 GMT

I have made sure that this system has the latest QPK(March 2004) and also has all of the needed Java patches from the HP Java portal.

One thing I have found out now is that running the jre (/opt/java1.4/jre/bin/java) works fine until after Sybase 12.0 starts on this K380. The server has 4 240Mhz CPU's and 3GB of RAM.

Once the database server starts, the system still has over 600MB of RAM free but I still get the following error:

/usr/lib/dld.sl: Call to mmap() failed - TEXT /opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl
/usr/lib/dld.sl: Not enough space
Abort(coredump)

Any other ideas?

Much appreciated!

Re: jre core dumps after install

Mike Stroyan — Wed, 21 Jul 2004 14:58:37 GMT

It sounds like Sybase has consumed almost all of the available 32-bit shared memory address space. There isn't enough space left to map the shared libraries.There are a couple of interesting ways to work around that problem.

You could use "java -d64" to request the 64-bit java. That would get away from 32-bit limits. It would not be able to use 32-bit jni libraries.

You could request a really big maximum heap value with "java -Xmx2500m". That would have the rather unexpected side-effect of making java use a java process with private mapping in both the third and forth quadrant. It would avoid the shared space conflict by having private copies of all shared libraries.