A reconnect to SQL Server group cluster should work after the SQL Server node has changed

Current Situation

• A SQL Server node in a group cluster stopped working so that the JobScheduler DB is moved to another SQL Server node
• JobScheduler tries to reconnect repeatedly unsuccessful

  2017-09-10 20:29:48.878+0200 [info]   (Database) SCHEDULER-957  Closing database
  2017-09-10 20:29:48.878+0200 [ERROR]  SCHEDULER-303  Problem with database: SCHEDULER-360  Error when accessing database table order history [Z-JAVA-105  Java exception com.microsoft.sqlserver.jdbc.SQLServerException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond, method=executeUpdate [] / sos::scheduler::order::Order::db_update_order_step_history_record] [sos::scheduler::order::Order::close_log_and_write_history]
  2017-09-10 20:29:48.878+0200 [info]   (Database) SCHEDULER-907  Opening database: jdbc -id=spooler -class=com.microsoft.sqlserver.jdbc.SQLServerDriver jdbc:sqlserver://xxx:1433;sendStringParametersAsUnicode=false;selectMethod=cursor;multiSubnetFailover=true;IntegratedSecurity=true;databaseName=xxx
  2017-09-10 20:29:48.893+0200 [info]   (Database) SCHEDULER-807  Using database product Microsoft SQL Server
  

• The connection is back after restarting the JobScheduler.

Desired Behavior

If the node of a SQL Server cluster has changed then a reconnect should work without a JobScheduler restart