JobScheduler should check the scripting language compatibility at run-time

• Current Situation
  • If an x64 Master JobScheduler (64bit) is used with an x86 Agent (32bit) and a job is assigned the script language "javascript" then the Master JobScheduler throws an error:

    SCHEDULER-482  Language 'javascript' is not supported on 64 bit. Please check the script element.
    2014-10-21 18:00:04.886+0200 [info]   SCHEDULER-902  state=stopping"
    

  • This behavior is due to the fact that the scripting language "javascript" (SpiderMonkey) is available exclusively for 32bit JobScheduler instances. The Master JobScheduler checks the scripting language when loading the job configuration and denies scripting languages that are not available on the Master JobScheduler's platform.
• Desired Behavior
  • The Master JobScheduler should not check the JavaScript compatibility when loading the job configuration. At that point in time it is not yet decided on which JobScheduler Agent a job will be executed.
  • Instead the JobScheduler Agent should check the scripting language compatibility at run-time.
• Hints
  • Use of the scripting language "javascript" (SpiderMonkey) will become deprecated in the near future with the availability of the JobScheduler Universal Agent (JS-1291).
  • We recommend to switch to scripting languages that are available with the JVM. Depending on the Java version this could be Rhino (Java 7) or Nashorn (Java 8). This scripting language is addressed by using the configuration element <script language"java:javascript">.
  • See What are the differences between the SpiderMonkey, Rhino and Nashorn scripting engines?

To reproduce the problem please check the attached JobConfiguration.