JVM memory of job

[martin_eberle]

Hi

I had a problem with max. memory used by the dispatcher to work on his jobs.

Job terminated with an error similar to "not sufficient memory"

Open "Dispatcher_template.prop" in the install directory and extend the javaoptions to:

JAVAOPTIONS=-Xmx512M

Open Idm Center and Regenerate the dispatcher scripts and stop / start the dispatcher.

=> Then the java process should be started with 512 MB maximal RAM. This solved my problem.

Martin

[former_member207428]

Hi Martin,

we had the same issue on our IdM 7.1 SP1 environment when running the "AS ABAP - Initial Load" job. I created a customer message to SAP, where they responded I should add the following :

JAVAOPTIONS=-Xmx512M -Xms512M

After restarting the dispatcher, whatever job I choose to run, it always stated 'Idle'.

Removing the additional parameters resulted in a running job.

Apparently only the -Xmx parameter may be added, otherwise the jobs will stay idle.

Best regards & thanks for posting,

Kevin

[Former Member]

If you want to use more than one parameter in the -JAVAOPTIONS you should set the

MXDISPATCHER_EXECSTRING to "1" . (MXDISPATCHER_EXECSTRING=1)

Roy Tronstad