cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Builder Memory Consumption

Former Member
0 Kudos

Hello,

we are experiencing very high memory consumption of the Java IR designer (not the directory). Especially for loading normal graphical idoc to EDI mappings, but also for normal idoc to idoc mappings. examples (RAM on client side):

- open normal idoc to idoc mapping: + 40 MB

- idoc to edi orders d93a: + 70 MB

- a second idoc to edi orders d93a: + 70 MB

- Execute those mappings: no additional consumption

- third edi to edi orders d93a: + 100 MB

(alle mappings in same namespace)

After three more mappings RAM on client side goes on 580 MB and then Java heap error. Sometimes also OutOfMemory, then you have to terminate the application.

Obviously the mapping editor is not quite will optimized for RAM usage. It seems to not cache the in/out message structures. Or it loads for every mapping very much dedicated functionality.

So we cannot really call that fun. Working is very slow.

Do you have similar experiences ? Are there workarounds ? I know the JNLP mem setting parameters, but the problem is the high load of each mapping, not only the overall maximum memory.

And we are using only graphical mappings, no XSLT !

We are on XI 3.0 SP 21

CSY

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

close without answer

former_member192295
Active Contributor
0 Kudos

Hi,

It is basis related problem check with them they can sort out easily after that if have any problem we can do in table sizing etc modification. Most of the cases sort out in hardware sizing.

former_member183906
Active Contributor
0 Kudos

Hii

Apart from raising tablespace..

Note 425207 - SAP memory management, current parameter ranges

you have configure operation modes to change work processes dynamically using rz03,rz04.

Please see the below link

http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a7f53505211d189550000e829fbbd/frameset.htm

You can Contact your Basis administrator for necessary action

Former Member
0 Kudos

Thanks for the answers, but the problem is about CLIENT memory, not the XI backend !

CSY

Former Member
0 Kudos

Need to increase the tablespace of XI