EP_SHUTDOWN message received after application server abruptly shutdown

Products

• Autosys Workload Automation

Issue/Introduction

Below entries were seen in the application server logs, before the application server aborted. 

[01/01/2026 10:12:25]      CAUAJM_W_30100 Request has expired after 61 seconds. Discarding...
[01/01/2026 10:12:25]      CAUAJM_W_30036 Client [AutoSys Sendevent:12345][16][##########] [0x25acgg0][01/01/2026 ######] API ID [122] request discarded.
[01/01/2026 10:12:26]      CAUAJM_I_30033 Client [AutoSys Sendevent:12345][16][#########] session ended.
[01/01/2026 10:12:28]      CAUAJM_E_10641 Trouble reconnecting to database, database monitoring system cannot continue any longer.  Exiting!
[01/01/2026 10:12:28]      CAUAJM_I_10667 Notification completed successfully.

The scheduler itself was not shutdown. Why was the notification titled EP_SHUTDOWN?

 

Cause

When app server experienced below message, as it could not function anymore as the underlying database connection was not available anymore, it triggered the EP_SHUTDOWN notification as part of the abort.

"[01/01/2026 10:12:28]      CAUAJM_E_10641 Trouble reconnecting to database, database monitoring system cannot continue any longer.  Exiting!"

 

Resolution

This is expected.  This message is shared between app server and scheduler, so EP_SHUTDOWN is OK there, though it is a bit misleading.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.