Insufficient space in Javaheap

,
1

System Details:
Mediator : 7.4.1
OS : AIX 5.3 - 64 bit - RAM 2GB
Tomcat - 4.1.30
Sun JDK 1.4.2

When we start the Host manager using startHostManager.sh script, we get a Java heap error as show in the xbdhost.log. In one of the discussion it’s been mentioned to set two variables

  IBM_HEAPDUMP_OUTOFMEMORY=false
  DISABLE_JAVADUMP=true

which is by default set in mediator version 7.4.1. And also its been mentioned that the dump has no implications on the functionality but when we make a request to the mediator for a sequence, the request gets timed out and Tomcat through OutOfMemory as shown in Catalina.out.

The start up script hasn’t been modified, it’s same been deployed.

-------------- xbdhost.log --------------------
2005-09-29 01:15:02 PM CDTINFO: EntireX XML Mediator Version 7.4.1.1
2005-09-29 01:15:02 PM CDTINFO: Copyright (C) 2000-2004 Software AG. All rights reserved.
2005-09-29 01:15:02 PM CDTINFO: calling register for expsag01
2005-09-29 01:15:02 PM CDTINFO: Creating rmi registry at port 20050
2005-09-29 01:15:02 PM CDTINFO: rmi registry started successfully at port: 20050
2005-09-29 01:15:02 PM CDTINFO: Registering expsag01 at port 20050
2005-09-29 01:15:02 PM CDTINFO: expsag01 registered at port:20050:expsag01
2005-09-29 01:15:02 PM CDTINFO: Done registering for expsag01
2005-09-29 01:15:03 PM CDTINFO: HostManager received startFactory Request for <>
2005-09-29 01:15:03 PM CDTINFO: HostManager <> is Starting…
2005-09-29 01:15:11 PM CDTERROR: JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMST109: Insufficient space in Javaheap to satisfy allocation request
2005-09-29 01:15:15 PM CDTINFO: HostManager <> is started.
2005-09-29 01:15:15 PM CDTINFO: HostManager startFactory for <> is successful, Factory is started

---- Catalina.out --------------------
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
.JVMDG318: Heap dump file written to /usr/sag/exx/v721/3rdparty/jakarta-tomcat-4.1.30/bin/heapdump303266.1128017857.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /usr/sag/exx/v721/3rdparty/jakarta-tomcat-4.1.30/bin/javacore303266.1128017859.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
.JVMDG318: Heap dump file written to /usr/sag/exx/v721/3rdparty/jakarta-tomcat-4.1.30/bin/heapdump303266.1128017864.phd
JVMDG303: JVM Requesting Java core file

Thanks in advance for the solution :slight_smile:

2

This appears to be a problem with the IBM JVM itself. There is an open issue at IBM “SOV,94351” opened the end of August. I do not beleive a solution is going to be provided in the short-term for this.

You could try going back to the IBM JVM in 1.4.1 or if possible, switch to the sun JVM 1.4.2_(Newest). In my reading about the issue, it was not clear at what point IBM introduced the bug. They made some changes to the Garbage collection in recent releases which caused this issue.

I hope that helps 8=)

3

Did you ever get a solution to your “JVMST109: Insufficient space in Javaheap to satisfy allocation request” error? We are having the same problem with our installation of Mediator on a zSeries Linux image. Our java is now at version:

java version “1.4.2”
Java™ 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxz64142-20061124 (SR7) (JIT enabled: jitc))

It is not possible for us to go back to the SR3 release because we get our OS and Java from Novell, and they don’t support that release. Besides, if it was fixed at SR3, shouldn’t the problem have been solved when we were at SR4 and now at SR7?

Any help would be greatly appreciated.
Best regards,
Karin Hilbert

4

Hi

I have the same problem. Looks like it can be solve by modifying the following variables:

-Xms<size>        Set initial Java heap size
-Xmx<size>        Set maximum Java heap size

that controls the java call for Websphere to a higher value. I cannot manage to set them using the variable JAVA_OPTS and cannot find where to modify the java command in the /opt/WebSphere_v61/bin/startServer.sh command.

Any idea ?

TIA