Daily Plan submission rolled back in case of session renewal in Controller connection

Current Situation

• The JOC Cockpit connects to the Controler by use of an internal API that is based on sessions.
  • Sessions use an idle timeout of 1 hr. after which they have to be renewed.
  • On session renewal the Controller reports the problem: Invalid session token. As this is not a problem but normal behavior, the Controller's related log output was moved to debug level with JS-2210.
• It remains the fact that occurrence of session renewal causes the next operation performed on the Controller to fail. This preferably affects the Daily Plan Service that is running in off-peak times that are more frequently hit by session expiration.
• If the Daily Plan Service meets session renewal of the Controller connection, then its operation to submit planned orders can be affected and will result in no orders being submitted for the next day. The problem is not detrimental for users who use Daily Plan settings to submit orders a number of days ahead. Users who submit orders just for the next day, will be affected.

Desired Behavior

• Session renewal is forced by a preliminary operation in the Daily Plan Service.
• As a result, next operations to submit orders will find a valid session,

Workaround

• Users can apply the following setting to the Controller instances' ./config/controller.conf file:

  # Idle Session timeout for JOC Cockpit sessions
  js7.auth.session.timeout = 24h
  

• Controller instances must be restarted to apply the setting.