Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
You should increase the Java heap space if JobScheduler reports out of memory Java exceptions (java heap space). The message in the log file looks like follow
Code Block |
---|
Com_set_error("Z-JAVA-105 Java exception java.lang.OutOfMemoryError("Java heap space"),
method=spooler_process()Z []","Remote_module_instance_server::step)
|
...
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
Code Block |
---|
<job<job 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:
Code Block |
---|
[java]
options = -Xmx512m
|
You can also set more Java options. For example you can set the initial and maximum Java heap space with:
Code Block |
---|
[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