Details
-
Fix
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Works as designed
-
1.13
-
None
Description
Current Situation
In JS-1748 is explained that the attribute "job_options" can be used to set Java options for any job starts. When adding this setting to the configuration file sos.ini, this has no effect. It only works when having this setting in the configuration file factory.ini.
Desired Behavior
It should be possible to set the Java options for all jobs with the "job_options" setting as explained with JS-1748
Workaround
- Stop JobScheduler Master
- Open the file %SCHEDULER_HOME%/bin/jobscheduler_environment_variables.cmd
- Change the line
set SCHEDULER_START_PARAMS=%SCHEDULER_PARAMS% -pid-file=%SCHEDULER_PID% -job-java-options=-Xmx1024m
e.g. to
set SCHEDULER_START_PARAMS=%SCHEDULER_PARAMS% -pid-file=%SCHEDULER_PID% -job-java-options=-Xmx10m
- In Windows
- Open a shell and navigate to %SCHEDULER_HOME%/bin
- Reinstall the Windows Service by executing the commands
- jobscheduler.cmd remove
- jobscheduler.cmd install
- Start JobScheduler Master
Maintainer Notes
- This issue has been raised due to a misunderstanding and wrong documentation in
JS-1748that explains that any of the configuration files ./config/factory.ini and ./config/sos.ini can be used for such settings. - In fact only the file ./config/factory.ini can be used to set Java options for jobs. It is recommended to use ./config/factory.ini for any Java options.
Attachments
Issue Links
- is related to
-
JS-1748 Different JAVA options in factory.ini for JobScheduler process and other process
- Released