Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.12.6
-
None
Description
Current Situation
When a YADE4DMZ job runs standalone (not in a job chain) a nullpointer exception is raised.
2018-11-01 17:10:36.075+0100 [info] [stdout] 01 17:10:36.069 [ERROR] (SOSJade4DMZJSAdapter.java:77) - SOSJade4DMZJSAdapter ended with error: java.lang.NullPointerException 2018-11-01 17:10:36.075+0100 [info] [stdout] java.lang.NullPointerException 2018-11-01 17:10:36.075+0100 [info] [stdout] at sos.scheduler.jade.SOSJade4DMZJSAdapter.doProcessing(SOSJade4DMZJSAdapter.java:152) 2018-11-01 17:10:36.075+0100 [info] [stdout] at sos.scheduler.jade.SOSJade4DMZJSAdapter.spooler_process(SOSJade4DMZJSAdapter.java:75)
Desired Behavior
YADE4DMZ should run standalone without throwing a null pointer exception
Maintainer Note
This Issue has been introduced with YADE-522
Attachments
Issue Links
- responds to trouble ticket
-
YADE-529 YADE throws a null pointer exception when running standalone
- Released