Using the configuration monitor without having node parameters should not produce file not found exception with stacktrace

When using the configuration monitor without having node parameters there is file not found exception with a stacktrace. As it is possible to use the configuration monitor in this way, there should not be this stacktrace.

java.io.FileNotFoundException: /home/test/scheduler.current32... (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileReader.<init>(Unknown Source)
at com.sos.JSHelper.io.Files.JSFile.Reader(JSFile.java:315)
at com.sos.JSHelper.io.Files.JSFile.getContent(JSFile.java:1106)
at sos.scheduler.managed.configuration.ConfigurationBaseMonitor.initConfiguration(ConfigurationBaseMonitor.java:180)
at sos.scheduler.managed.configuration.ConfigurationBaseMonitor.initConfiguration(ConfigurationBaseMonitor.java:156)
at sos.scheduler.managed.configuration.ConfigurationBaseMonitor.initConfiguration(ConfigurationBaseMonitor.java:141)
at sos.scheduler.managed.configuration.ConfigurationBaseMonitor.prepareConfiguration(ConfigurationBaseMonitor.java:229)
at sos.scheduler.managed.configuration.ConfigurationOrderMonitor.spooler_process_before(ConfigurationOrderMonitor.java:135)