Java Heap dump error

[former_member199619]

Hi,

We are running SAP WM 6.1 on SMP version: 3.0.8.3 SP level: 08.

We are getting heap dump error (below logs generated) while publishing the Agentry version from SMP cockpit. This version publish is done and is showing under the Published versions list and this version is there in production folder inside the configuration folder . After SMP server restart published version is getting deleted.

   :    [8112]  09:53:18    ***ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

java.lang.OutOfMemoryError: GC overhead limit exceeded

   :    [8652]  09:53:22    ***ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

   :    [4904]  09:53:26    ***ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

Dumping heap to ./log/heap_dump.hprof ...

   :    [2668]  09:53:31    ***ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

Heap dump file created [6705493333 bytes in 43.053 secs]

   :    [8288]  09:54:18    ***ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

We have only one Agentry application and we are facing this issue in our development environment. We have the same java heap configurations in Quality and Production environments, there we don't have any issue. We published Agentry version in our development environment so many times we have not faced this issue earlier. All of sudden we are getting this issue.

We upgraded our SMP server to 3.0.9.1 SP level: 09 even though we are facing the same issue.

-Shyam

[mark_pe]

Shyam,

Hi. This is documented in our SAP KBA note # 2230825 - Unable to upload the Agentry application with the error "OutOfMemoryError".

Best Regards,

SAP Mobile Support Team

[former_member199619]

Hi Mark,

Thanks for your reply.

We have upgraded our SMP server to SMP 3.0 SP09 PL2, even though we are facing same issue:

ERROR (:0): OutOfMemoryError: Could not allocate 0bytes

Regards,

Shyam

[Kevin_SAP]

You need to get a Heap Dump and figure out what is taking so much memory using Memroy Analyzer Tool (MAT).  Here are some older links for MAT instructions.  Since this is 3.0, you don't need psexec as the second 2 links are instructions for 2.x MBO runtime.

http://wiki.scn.sap.com/wiki/display/Java/Java+Memory+Analysis?original_fqdn=wiki.sdn.sap.com

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=388793187

http://wiki.scn.sap.com/wiki/display/SAPMOB/Java+Memory+Analyzer+with+SUP+and+SMP

[Former Member]

How much ram is on Dev server VS the QA server?

[Former Member]

Shyam,

Also configure below details in Management cockpit

(-XX:NewSize=420m)

(-XX:MaxNewSize=420m)

(-XXMaxPermSize=512M)

(-XX:PermSize=512m)

Xmn1024m

Xmx2560m

Ajitesh

[former_member199619]

Hi Stephen,

16 GB in DEV

32 GB in QA.

-Shyam

[former_member199619]

Hi Ajitesh,

Our current configurations are like below:

-Xms8192M

-Xmx8192M

-XX:PermSize=256M

-XX:MaxPermSize=512M

-Shyam

[Kevin_SAP]

I believe this is a known issue in that release (memory growth).  I would advise upgrading to SMP 3.0 SP09 PL03.

You can always get a Java dump (hprof) and look at the memory, but easier to upgrade.

Regards,

Kevin

[former_member199619]

Hi Ajitesh,

How can we analyse how much heap size we have to allocate ?

-Shyam

[Former Member]

Navigate to SMP Server's java bin folder and execute following command from command prompt

Jconsole.exe (1 space) <Java PID>

Here Java PID means running Java's PID number. you can get this from Task Manager details screen.

It will open a new window there click on "Insecure connection" and navigate to Memory tab. Here you can see total consumed Heap memory as well as load. Here you can also perform GC(Garbage collection) operation.

Thanks

Ajitesh

[Kevin_SAP]

If you have issues connecting to jconsole, you may need to add:

-Dcom.sun.management.jmxremote=true

To your props.ini in JVM settings(backup file first).

Regards,

Kevin

[former_member199619]

Hi Ajitesh,

Below are the memory usage screenshots. In VM Summary tab, it is showing as

current heap size = 3,850,632 kbytes

Maximum heap size = 7,797,248 kbytes.

This heap size is not enough? Do we need to increase the maximum heap size further more?

Here I performed GC also. After that also there is no change in heap memory usage.

-Shyam

[Former Member]

Shyam

Are you using cluster? current heap is consuming ~3gb which is quite big. I think  you have to increase your system memory and also please upgrade to latest version of SMP server. latest is SP09 PL03.

Ajitesh