JOC Cockpit should support long values for the session timeout

Current Situation

• When the value for a session timeout in the shiro.ini.active configuration file is bigger than the highest integer value (2147483647) then the automatic refresh in JOC Cockpit no longer works.

Desired Behavior

• It should be possible to define the biggest long value (9223372036854775807) for the session timeout and the automatic refresh in JOC Cockpit should still work.

Test Instruction

• Test Configuration
  • Copy the file shiro.ini.active to shiro.ini in the ./resources/joc directory of JOC Cockpit.
  • Modify the session timeout like this:
    securityManager.sessionManager.globalSessionTimeout = 9223372036854775807
  • Setup a job chain that includes 3 jobs to be executed in sequence and that sleep for 60s each.
• Test Execution
  • Basic Test Execution
    • Login to JOC Cockpit
    • Start the job chain
    • Remain in the Job Chains view and do not touch anything.
  • Negative Test Execution
    • With release 1.12.6 the view is not updated when the order moves through the job chain.
  • Positive Test Execution
    • With release 1.12.7 the view is refreshed when the order moves through the job chain.