High Port Values in xFlow clustering
search cancel

High Port Values in xFlow clustering


Article ID: 257910


Updated On:


CA Service Management - Service Desk Manager CA Service Desk Manager


Why is xFlow attempting to allocate high port values.  An example entry in the incidentMS.log shows attempts to access port 57845:

WARN - 20XX-XX-XX 16:12:29 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@XFLOW-SERVER-2.DOMAIN.COM:57845] - Couldn't join seed nodes after [3134] attempts, will try again. seed-nodes=[akka.tcp://Incident_MicroService_XflowClusterSystem@XFLOW-SERVER-1.DOMAIN.COM:2551, akka.tcp://[email protected]:2551]



CA Service Management - xFlow

17.3 and 17.4


The Play framework, which is responsible for xFlow, has been upgraded to a newer version to remediate vulnerabilities..

As part of this upgrade, port 2552 which was used for cluster management has been upgraded to 25520 (from Play Framework itself).

The high numbered port numbers (25520...) are from the playframe work itself which cannot be configured.

Additional Information

For Reference check out the content under Remoting Section: