JAVA Heap Size Error in SAP Work Manager

[Former Member]

We are getting the below error wrt Java Heap size in the SAP Work manager Application:

"

2014/08/08 00:48:56.142:setImportParameters::STORAGE_REF_KEY=ET_COMPLEX_TABLE

2014/08/08 00:48:56.143: + User=MAINTMGR

2014/08/08 00:48:56.143: execute::::MAINTMGR::before BAPI execute: /SMERP/MM_CTMATPLANT_GET

2014/08/08 00:55:20.905: + BackEnd=Java-1

2014/08/08 00:55:20.905: Exception while updating complex table 'ctpart': JavaBackEndError: JAVA EXCEPTION CAUGHT: java.lang.OutOfMemoryError: Java heap space in AgentryJavaComplexTableIterator::hasNext at AgentryJavaComplexTableIterator.cpp:52

2014/08/08 00:55:21.099: + Thread=6588

2014/08/08 00:55:21.099: + Thread Pool=Server

2014/08/08 00:55:21.099: + WorkFunction=00000000020DEF90

2014/08/08 00:55:21.099: + User=MAINTMGR

2014/08/08 00:55:21.099: + User=MAINTMGR

2014/08/08 00:55:21.099: Received Logout Request message 18 status changed to 'In Progress'

2014/08/08 00:55:21.105: Logged out (but not yet cleaned up)

"

We have tried to increase the initial and maximum heap size in the Agentry.ini file from 256 / 512 to 512 / 2048 respectively. But the

error still persists.

Can you please let us know if there are any

other changes required for

the same?

PFA the Java backend and the user

logs. Please treat this ticket with

the highest priority.

Thanks,

Boopalan

[Former Member]

Thanks for the reply stephan, Manju,

We have 500K rows in executing backend bapi

we have not set any filter setings

other users also getting same error

we are using Work Manager 6.0 in SMP2.3 sp4..

is there any config filter available to get the 500k data from parts..

Thanks,

Boopalan M

[stephen_kringas]

Hi Boopalan M,

To filter the data coming down to the mobile application refer to the Work Manager 6.0 Configuration Guide (S-User required)

Section 3.10.3 covers Data Filtering on MDO's via the Syclo Configuration Panel.

Cheers,

Stephen

[i834235]

Looks like ur getting   heap size error while trying to fetch  records for ctparts complex table. From platform  point of view you have increased heap size. Next step is to analyze application settings for ctparts  complex table. As indicated by Steve from application point you need check the need for  amount of materials your trying to retrive , can you set filter for ctparts ,  does  ctparts  BAPI execute in SAP without any timeout error.

What is the version of Work Manager your using ?    With WM 6.1 you have options to  take advantage of data staging that is delievered as part of standard application.

Thanks

Manju.

[Former Member]

" Please treat this ticket with the highest priority.

" The SCN is not a support, so there are not tickets.  People from that work with the software will answer questions when they have time and to their ability. 

Have you ran the bapi in the backend just to see how many rows are being returned?
Have you tried filtering the data?

Are other users getting the same issue?

Stephen