Support Article
NodeType nodes are set as 'Untyped' on startup
SA-80216
Summary
The -DNodeType is applied to the JVM argument to classify a Pega node within the cluster.
During the startup, the NodeType value is ignored and error displays. As a result, the Node type is set to 'Untyped'.
Error Messages
Error in the PegaRULES.log file
(internal.NodeClassificationImpl) ERROR - Ignoring Invalid NodeType passed: ADM
(internal.NodeClassificationImpl) ERROR - Ignoring Invalid NodeType passed: PegaMKTEmail
(internal.NodeClassificationImpl) ERROR - Provided NodeTypes: ADM,PegaMKTEmail is not Valid. Hence turning off NodeClassification
90 -DNodeType=Custom1 -Djava.awt.headless=true -Djava.security.properties=/usr/local/tomcat/conf/java.security.overwrite -Djdk.tls.ephemeralDHKeySize=2048 -Dpega.logdir=/usr/local/tomcat/logs -Didentification.nodeid=ADM-i-0a264372e9c782a4a -Dindex.directory= -DNodeType=ADM,PegaMKTEmail -DapplicableNodeTypes=WebUser,BackgroundProcessing,BIX,Search,Batch,Custom1,Custom2,Custom3,Custom4,Custom5,RealTime,Stream,DDS,ADM,RTDG,PegaMKTEmail,PegaMKTSMS -
Steps to Reproduce
Pass the -DNodeType JVM argument with Pega standard values such as, Search, Background, Custom1, etc.
Root Cause
The -DNodeType argument was passed twice to the whole argument set. Because of this duplicate entry, the later values are ignored and the classification led to the error.
Resolution
Retain only the -DNodeType argument. If multiple values must be set, use a comma separated format as below:
-DNodeType=Batch,Search,....
Published August 15, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.