Repeat notifications stop running in Cluster environment (TS_THREADID gets stuck)

ID:    D27953
Published:    16 March 2023

Defect Id


Originally Reported Against

SBM 12.0




If Tomcat is stopped while the notification engine is running, the TS_THREADID values in the TS_NOTIFICATIONEVENTS table will be stuck. After this, the notification will no longer run, and users will not receive emails for these events. This has been seen mostly with scheduled reports but can also happen with repeating notifications. 

This problem only happens when running the Notification Server as a cluster. 

Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs