Defects

SBM 12: Load balance / Cluster Tomcat with Notification Engine stops responding



ID:    D27847
Published:    23 June 2022
Updated:    07 July 2022
 

Defect Id

DEF346858

Originally Reported Against

SBM 11.8

Assigned To

SBM 12.1

Status

In Progress

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 1: Restart the Tomcat service on both servers, then start the Notification Server only on one node. However, this means the Notification Server is no longer load balancing across nodes.

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.

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