JOC Cockpit - Troubleshooting

Database Connections to MySQL unavailable after idle timeout

If a MySQL DBMS is being used by the JobScheduler, then the MySQL wait_timeout that rules the max. lifetime of idle connections should be checked and if necessary modified. 

• The default wait_timeout for MySQL is relatively short and the JOC Cockpit does not have a mechanism for keeping the connection open over longer periods of time such as overnight. 
• See the following article for instructions about how to change the MySQL DBMS timeout variable:
  • Database Connections to MySQL get lost
• If the DBMS wait_timeout is too short users will get an "Unauthorized to access JOC Cockpit" message together with a JOC-407 error message after submitting their credentials. However, restarting the JOC Cockpit web service / daemon will create a new database connection and allow authorized users to log in again.