Page History

...

You should increase the Java heap space if JobScheduler reports out of memory Java exceptions (java heap space) when executing non-Java orders. The message in the log file looks like follow

 Com_set_error("Z-JAVA-105 Java exception java.lang.OutOfMemoryError("Java heap space"),
 method=spooler_process()Z []","Remote_module_instance_server::step)

There are two ways for increasing the available Java heap space. You can do it for only one job separately or you can apply the increment for all jobs.

Please note:

If you increase the initial heap space (-Xms) for all jobs you could run into memory troubles if you are running to much Java tasks at one time.

In most cases it is enough to apply just a maximum Java heap space with -Xmx.

Increment for only one Job using Java

If you want to increase the heap space for only one Job you can do it in the job configuration: http://www.sos-berlin.com/doc/en/scheduler.doc/xml/job.xml#attribute_java_options

 java_options = "-Xmx512m"

Increment for all Jobs using Java

You can increase the maximum Java heap space (set by the JobScheduler when starting the Java VM) within the configuration file sos.ini, for example:

 [java] 
 options = -Xmx512m 

You can also set more Java options. For example you can set the initial and maximum Java heap space with:

 [java] 
 options = -Xms128 -Xmx512m 

For possible java vm options please see java VM documention http://download.oracle.com/javase/1.5.0/docs/tooldocs/windows/java.html#options