Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Stream service cannot start on second node on same host

SA-96525

Summary



A new Pega instance is set up in addition to the existing instance in the same node. To start the new Pega instance, user changed port numbers defined in the server.xml,  prconfig.xml and Dynamic System Settings for Stream Service (For more information, refer to: Advanced configurations for the stream service https://community.pega.com/knowledgebase/articles/advanced-configurations-stream-service.).
The new node works correctly, however, the Stream Service does not work.


Error Messages



"Stream service is down" in Admin Studio. JOINNING_FAILED in Decisioning > Infrastructure > Stream


Steps to Reproduce

  1. Set up a Pega instance (Tomcat + PostgreSQL).
  2. Set up another Pega instance in the same host (Operating System) with a different port by configuring server.xml, prconfig.xml, and DSS (JMX port and so on).


Root Cause



The new node  had a port issue.


Resolution



Perform the following local-change:

For multiple JVMs running on the same machine, change the port used by the stream on every server.

Ensure the following prconfig settings are unique for each stream node and restart the JVMs:
  • dsm/services/stream/pyBrokerPort (default9092)
  • dsm/services/stream/pyKeeperPort (default 2181)
  • dsm/services/stream/pyJmxPort ( default 9999)
  • dsm/services/stream/pyPort (default 7003)
Suggest Edit

Published January 17, 2020 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us