SAP Knowledge Base Article - Preview

2974453 - Cockpit failed to start due to the message "Failed to start AlertService" - SAP ASE

Symptom

Cockpit failed to start because alert server failed to start.

[INFO ] [alert.AlertService                           ] [main] - About to start the alert server.
[ERROR] [kahadb.KahaDBStore                           ] [ActiveMQ Broker[COCKPIT-4993] Scheduler] - Failed to load message at: 1:68658
java.io.IOException: Unexpected error on journal read at: 1:68658
Caused by: java.io.EOFException
[ERROR] [cursors.AbstractStoreCursor                  ] [ActiveMQ Broker[COCKPIT-4993] Scheduler] - Failed to fill batch org.apache.activemq.broker.SuppressReplyException: ShutdownBrokerInitiated
[ERROR] [services.Agent                               ] [main] - Failed to successfully start agent: Failed to start AlertService.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE)
  • SAP ASE Cockpit
  • Microsoft Windows

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Cockpit, KahaDB, alert server, message broker , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.