Defects
Repeat notifications stop running in Cluster environment (TS_THREADID gets stuck)
| ID: | D27953 | |
| Published: | 16 March 2023 |
Defect Id
DEF348003
Originally Reported Against
SBM 12.0
Status
Submitted
Description
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.
