How to check your Hazelcast port
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Hazelcast is a third-party technology that is used when Confluence Data Center is installed in a cluster. It is used by Confluence and Synchrony. For details on those ports, check the document below:
Hazelcast port for Confluence
The Hazelcast port for Confluence can be changed by using the confluence.cluster.hazelcast.listenPort system property. See Configuring+System+Properties to find out the various ways system properties can be set in your site.
If the confluence.cluster.hazelcast.listenPort system property is not present, the Hazelcast port for Confluence will default to port 5801.
Hazelcast port for Synchrony
The Hazelcast port for Synchrony can be changed by using the cluster.listen.port property. The way this property is passed to Synchrony depends on how you run Synchrony.
- If you run a Synchrony standalone cluster, the Hazelcast port is customized by adding the
cluster.listen.portproperty in thestart-synchrony.shorstart-synchront.batscript. - If you use managed Synchrony, the Hazelcast port is customized by adding the
cluster.listen.portproperty to thesynchrony-args.propertiesfile.
If the cluster.listen.port property is not present, the Hazelcast port for Synchrony will default to port 5701.