PI Heap memory issue

[Former Member]

Hi,

When I try to take an export (R3load) for my PI 7.1 system, it terminates at the last step while exporting the Java schema @ table BC_MSG or BC_MSG_AUDIT (sometimes) with an out of memory error.

I've got ample RAM & heap space assigned ..plus the message delete job runs daily..

pls. helpp.

Thank You,

Have a nice day,

Saba.

[Former Member]

Hi Saba,

Was you problem resolved if not check these notes may help you,

Note 1173398

Note 1120872

Regards

Uday

[Former Member]

Thanks lot.

I was having the same issue and Error during expport of BC_MSG

These notes solved my problem.

Regards

Omkar

[Former Member]

Hi guys,

By applying Note 1173398 this solved my problem.

On short the solution will be:

If the problem occurs during a sapinst run (systemcopy for example), stop the sapinst, and edit control.xml.

Search for the line

   var jloadHeap = "-Xmx1024m";

and replace it by

   var jloadHeap = "-Xmx1540m";

Save control.xml.

Restart sapinst.

(It's not sufficient to just retry the phase, you have to restart the sapinst, otherwise control.xml isn't reread.)

Best regards,

Florin Radulea

[Former Member]

Hi Guys,

I know this is an old post but recently I had the same issue and note number 1276704 - jload export fails with java.lang.OutOfMemoryError. solved my issue.

log on to configtool and click on secure store and then on the right side of the screen click on URl and in the Value column at the end copy and paste this line, ";responseBuffering=adaptive" . save and exit.

next restart sapinst and be happy...

[Former Member]

Awesome, this works ! 🙂

[Former Member]

Thanks Syed, the note 1276704 worked for me too. Dont see anything to mark your answer correct but this is right note.

[sunny_pahuja2]

Could you please paste error log of this phase ?

Thanks

Sunny

[Former Member]

Hi,

Here it is:

SEVERE: Error during export of BC_MSG

FATAL: Main class "com.sap.inst.jload.Jload" cannot be started:

java.lang.OutOfMemoryError: Java heap space (failed to allocate 32 bytes)

at java.io.StringWriter.<init>(StringWriter.java:33)

at com.sap.inst.jload.Jload.logStackTrace(Jload.java:131)

at com.sap.inst.jload.Jload.printErrorInformation(Jload.java:139)

at com.sap.inst.jload.Jload.main(Jload.java:753)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:161)

FATAL: com.sap.engine.offline.OfflineToolStart will abort now with exitcode 2

Exception in thread "Thread-0" java.lang.OutOfMemoryError: Java heap space (failed to allocate 64 bytes)

at com.sap.engine.offline.FileClassLoader.close(FileClassLoader.java:1557)

at com.sap.engine.offline.FileClassLoader$1InternalHook.run(FileClassLoader.java:375)

Max heap size is 3 GB..RAM = 16 gigs.

Table BC_MSG is growing by leaps n bounds...evn though the message delete job runs daily.

Thanks,

Saba.

[Former Member]

Hello,

Please configure your system to generate a heapdump. The settings for the Sun JDK can be found in :

1004255 : Sun JDK

How can I get a heapdump ?

https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=33456

1267126 IBM i: How to get a heapdump which can by analyzed with MAT

1265455 How can you generate a system dump for analysis using MAT? (LNX)

1263258 LXN / 64

1259465 How to get a heapdump which can by analyzed with MAT (AIX)

(1053495 heapdump settings on AIX)

3G is already a higher setting and if the application is still failing with outofmemory, there might be a possibility of application leak. Heapdump (.hprof if SUN and .dmp or .phd if IBM) will help you identify the cause.

The heapdump can be analyzed using the MAT Tool which can be downloaded from www.eclipse.org/mat

You need the dump in either .hprof or .dmp to be able to use this tool.

Any changes from the above notes on your system will need you to restart the system for the changes to be effective.

Hope the above helps.

Best Regards,

Snehal Bhaidasna

Palo Alto, CA(USA)

[Former Member]

Please try

For dispatcher set maxheapsize and -Xms to 170-256 MB and for server set maxheapsize and -Xms to 2048

Windows page file is atleast 2 times of your RAM

Also refer to SAP note 723909

[Former Member]

Hi Guys,

Thanks..

These notes are for a 7.0 system..I'm on 7.1:((((

Thanks,

Saba.

[former_member255719]

Hi Saba,

Please let me know whether the issue you were facing related to PI 7.1 got resolved.

If yes then please let me know the resolution steps.

Thanks,

Mohan

[thunder_feng]

Hi Saba,

As per the error, I think this note can help you to solve the issue.

https://service.sap.com/sap/support/notes/994433

Best Regards,

Thunder