JagannathR8869 Member since 2016 43 posts
DXC Technology
Posted: January 24, 2018
Last activity: February 7, 2018

Nodes recover upon failure causing listeners to fail on it

Random Node of the cluster (upon any type of crash) try to recover but have the following issue after restart :

[.PRPCWorkManager : 2] [ STANDARD] [ MCOMSuper:01.42] (nector.Rule_Connect_JMS.Action) ERROR Rule-Connect-JMS.CCC-Int-Notify.SendNotificationMsgAgent - Caught unhandled exception: java.lang.UnsupportedOperationException: DEST_D_NULL< java.lang.UnsupportedOperationException: DEST_D_NULL

The above error causes that particular JMS-Connect to fail. Thus any messages that were supposed to be produced by it also.

We store the connection details in a declare page which if it fails to load during start up causes issues.

How do we go about preventing this during start up. ? Is there a way to fail the whole node if there were such failures to load during start up ?

System Administration Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn