confusing log line: ...unknown parameter java_options=

Current Situation

• For each job start you find the call in the ./logs/scheduler.log
  example

  /opt/sos-berlin.com/jobscheduler/scheduler.1.9/bin/scheduler  -sos.ini=/home/sos/sos-berlin.com/jobscheduler/scheduler.1.9/config/sos.ini  -ini=/home/sos/sos-berlin.com/jobscheduler/scheduler.1.9/config/factory.ini  -java-options=    -java-classpath=:  -O  -job=CheckDaysSchedule  -task-id=4329  -log=exception.* log4j.* >+/home/sos/sos-berlin.com/jobscheduler/scheduler.1.9/logs/scheduler.log  
  

  which contains -java-options= -java-classpath=:

• Some log lines later you see

  {scheduler} sos::scheduler::Com_remote_module_instance_server::Construct unknown parameter java_options= 
  {scheduler} sos::scheduler::Com_remote_module_instance_server::Construct unknown parameter java_class_path=
  

  where both command line options are valid.

• Both parameters are configured in the ./config/factory.ini
• The log output "unknown parameter" does not signal an error but is an internal information about the applicability of parameters.

Desired Situation

• An "unknown parameter" should be logged as being an "inapplicable parameter" in order to avoid any disambiguity concerning the informational nature of the log output.