Support Article
Incorrect behavior of nodes in Decision Services landing page
SA-58915
Summary
During the upgradation from Pega Marketing 7.2 to Pega Marketing 7.3.1, only local node displays as Active in Decision Services landing page when Pega Marketing application is deployed on multiple nodes. Each node has a distinct JVM dedicated to a specific role and is working fine.
Error Messages
066 [6f539.IO.thread-in-0] [ ] [ ] (nio.tcp.TcpIpConnectionManager) WARN - [somehostname]:5701 [bf28ebc210a8f805153ebf7a3c66f539] [3.8] Wrong bind request from [somehostname]:5701! This node is not requested endpoint: [127.0.0.1]:5701
Steps to Reproduce
- Upgrade from Pega Marketing 7.2 to Pega Marketing 7.3.1
- Click Add node in the Decision Services landing page
Root Cause
A defect or configuration issue in the operating environment. The prconfig file is incorrectly set to use hostname instead of IP address.
<env name="identification/cluster/public/address" value="somehostname" />
Resolution
Perform the following local-change:
Provide the IP address for inter-cluster communication.
<env name="identification/cluster/public/address" value="127.0.0.1" />
Published November 29, 2018 - 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.