SEVERE: java.lang.OutOfMemoryError

[Former Member]

Hi experts,

I get error SEVERE: java.lang.OutOfMemoryError in jload.log and jload.java.log when I Im running the online system export of ABAP+JAVA system.

I also see SEVERE:Error during export of BC_SLD_CHANGELOG in jload.java.log above the error of SEVERE: java.lang.OutOfMemoryError.

Any idea?

Thanks.

Regards,

Thava

[rajasekhar_reddy14 · Accepted solution]

I THINK it could be because of less heap memory , increase your virtual memory size.

Regards,

Raj

[Former Member · Accepted solution]

Hi,

How increase this. Please help.

Thanks.

Regards,

Thava

[former_member264034]

Hi,

The case is as the one reported in SAP note:

*1173398 - jload export fails with OutOfMemoryException

Alternatively I'd advice to reduce the size of

BC_SLD_CHANGELOG by the SLD directly.

For this you will have to log on to the sld by:

http://<hostname>:<http_port>/sld

-> Administration

-> Change Log

-> Reduce Size of Change Log

-> delete "obsolete" entries

The change log can grow very large in

a short period of time if not cleaned up regularly.

The entries in the table are only to log changes in SLD and are only

required in support cases.

Regards,

Aidan

[Former Member]

Hi,

Your reply was helpful but in note 1173398 mentioned look for var jloadHeap ="-Xmx1024m". I cant find this line. How to increase Heap Memory then?

Thanks.

Regards,

Thava

[former_member264034]

Hi,

As mentioned in the note this parameter should be in your control.xml

but this note is valid for the following:

Operating system NT

WINDOWS

Database system MSSQLSRV8.0

MSSQLSRV9.0

Question: are you using a 64 or 32bit OS? For 64bit, the recommended

value is 2048m for that parameter while for 32bit, the recomended value

is 1024m/1540m.

Regards,

Aidan

[Former Member]

Hi Aidan,

I have set the value to 2048m. Anything else to be set at the configtool? Please help as I still stucked at JAVA export step in system copy.

Thanks.

Regards,

Thava

[former_member278348]

Hi,

I encountered this error recently for Solman 7.1 while doing system copy for same table.

SAP Note 1276704 was helpful in solving this issue.

regards

Magi