Java heap size error Work manager

[Former Member]

Hi,

  We are working with Work Manager 6.0 running on SMP 2.3 SP03.

The application was working fine, but after the data load that has happened in the UAT

System, we are getting the below error:

"

2014/08/08 00:48:56.142:

setImportParameters::STORAGE_REF_KEY=ET_COMPLEX_TABLE

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

2014/08/08 00:48:56.143:                 execute::::TS_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=TS_MAINTMGR

2014/08/08 00:55:21.099:         + User=TS_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 tried to increase the min and max heap size from 256 / 512 to 512 /

2048 respectively in Agentry.ini, but are still getting the same error.

Please let us know if there is any other parameter which can be used to

fine tune this and get this up and running,

Thanks for the help.

[Former Member]

Raviraj,

Are you working with Boopaln?  The reason why I as He posted the same error (in the same complex table) With the same changes but just a different user shown.

If yes. please see that thread at: 

[Former Member]

Stephen,

             Thanks for the reply. Yes we are working together, in different time zone.

Thanks for pointing that out I will check that thread.

Regards,

Ravi.

[Former Member]

Hi Ravi,

We are facing a similar situation here. Can you please share any update on this issue.

Thanks,

Rakshit