Defects
SBM 12: Load balance / Cluster Tomcat with Notification Engine stops responding
| ID: | D27931 | |
| Published: | 30 January 2023 | |
| Updated: | 08 February 2023 |
Defect Id
DEF347812
Originally Reported Against
SBM 12.0
Resolved In
SBM 12.0 Hotfix
Description
With a load balance / cluster setup for Tomcat, if Notification Server is started on more than one node, all of Tomcat will stop responding. User browsers may lockup.
Resolution
This defect is causing a table lock issue.
Workaround Option 2:
- Stop Tomcat on both Notification Engine nodes.
- Delete all the rows in the NS_DUMPRECORDS tables.
- On the first node, go to Configurator > Mail Servers > Notification Server. Near the bottom, check the box for "Dump files storage type" and set it equal to "File System".
- Start Tomcat and the Notification Engine on this node, and wait a minute or two for it to begin processing.
- On the second node, go to Configurator > Mail Servers > Notification Server. Near the bottom, check the box for "Dump files storage type" and set it equal to "File System".
- Start Tomcat and the Notification Engine on this node.
