Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.11
-
None
Description
Current Situation
When using the configuration Monitor sos.scheduler.managed.configuration.ConfigurationOrderMonitor a null pointer exception is thrown. In the log the message error occurred in spooler_process_before: ConfigurationBaseMonitor: Monitor: error occurred preparing configuration: null (null) can be seen.
Desired Behaviour
The configuration Monitor should not throw a null pointer exception
Workaround
Use the new Implementation of the Configuration Monitor
com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor It is full compatible with the old one, works much faster and does not throw a null pointer exception.
The differences between the both implementations are described here
<job> <script language="shell"> <![CDATA[ echo hello world exit 0 ]]> </script> <monitor name="configuration_monitor" ordering="0"> <script java_class="com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor" language="java"/> </monitor> <run_time /> </job>