Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Failed to join a node to the Confluence data center


Hi everyone,

I'm trying to add a node to my Confluence data center instance and it's not working.

It shows me the following error screen every time I start the second node:

2022-03-01 15_13_06-Window.png

I've configured the second node with the steps that it puts in the Atlassian documentation, but the same thins happens constantly.

Both nodes see each other and have the correct ports open for hazelcast.

I show you a log trace:

2022-03-01 14:43:19,289 ERROR [Catalina-utility-2] [com.hazelcast.instance.Node] log [X.X.X.X]:5801 [node1] [3.12.11] Could not join cluster. Shutting down now!
2022-03-01 14:43:19,304 WARN [Catalina-utility-2] [com.hazelcast.instance.Node] log [X.X.X.X]:5801 [node1] [3.12.11] Terminating forcefully...
2022-03-01 14:43:19,373 WARN [Catalina-utility-2] [com.hazelcast.util.PhoneHome] log [X.X.X.X]:5801 [node1] [3.12.11] Could not schedule phone home task! Most probably Hazelcast failed to start.
2022-03-01 14:43:19,383 ERROR [Catalina-utility-2] [atlassian.confluence.setup.ConfluenceConfigurationListener] contextInitialized An error was encountered while bootstrapping Confluence (see below):
Node failed to start!
java.lang.IllegalStateException: Node failed to start!
at com.hazelcast.instance.HazelcastInstanceImpl.<init>(
at com.hazelcast.instance.HazelcastInstanceFactory.constructHazelcastInstance(
at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(
at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(
at com.hazelcast.core.Hazelcast.newHazelcastInstance(
at com.atlassian.confluence.cluster.hazelcast.HazelcastClusterManager.createHazelcastInstance(
at com.atlassian.confluence.cluster.hazelcast.HazelcastClusterManager.startCluster(
at com.atlassian.confluence.cluster.hazelcast.HazelcastClusterManager.reconfigure(
at com.atlassian.confluence.cluster.DefaultClusterConfigurationHelper.bootstrapCluster(
at com.atlassian.confluence.setup.DefaultBootstrapManager.afterConfigurationLoaded(
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(
at com.atlassian.confluence.setup.DefaultBootstrapManager.init(
at com.atlassian.config.util.BootstrapUtils.init(
at com.atlassian.confluence.setup.ConfluenceConfigurationListener.initialiseBootstrapContext(
at com.atlassian.confluence.setup.ConfluenceConfigurationListener.contextInitialized(
at org.apache.catalina.core.StandardContext.listenerStart(
at org.apache.catalina.core.StandardContext.startInternal(
at org.apache.catalina.util.LifecycleBase.start(
at org.apache.catalina.core.ContainerBase$
at org.apache.catalina.core.ContainerBase$
at java.base/ Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$ Source)
at org.apache.tomcat.util.threads.TaskThread$
at java.base/ Source)
2022-03-01 14:43:19,400 WARN [Catalina-utility-2] [atlassian.confluence.plugin.PluginFrameworkContextListener] contextInitialized Not starting full plugin system due to upgrade
2022-03-01 14:43:19,404 [Catalina-utility-2]
[Filter: profiling] defaulting to off [autostart=false]


2022-03-01 15:03:06,505 ERROR [http-nio-8090-exec-1] [confluence.setup.johnson.WebAppContextPathCheck] check Bootstrap did not initialize.
2022-03-01 15:03:07,111 ERROR [http-nio-8090-exec-2] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/data | traceId: 002ea5e546a3cafc
2022-03-01 15:03:07,428 ERROR [http-nio-8090-exec-3] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/fav-confluence.ico | traceId: 004aef73ef48139b
2022-03-01 15:03:23,335 ERROR [http-nio-8090-exec-4] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/data | traceId: 001ad67dd2d34887
2022-03-01 15:03:39,335 ERROR [http-nio-8090-exec-6] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/data | traceId: 00243042413d077f
2022-03-01 15:03:55,332 ERROR [http-nio-8090-exec-8] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/data | traceId: 00c8eb6277120fd3
2022-03-01 15:04:11,341 ERROR [http-nio-8090-exec-10] [atlassian.confluence.util.AbstractBootstrapHotSwappingFilter] doFilter Could not get swap target filter
-- referer: https://X.X.X.X/ | url: /johnson/data | traceId: 00c8d1ed86866447


I appreciate your help in advance.

1 answer

Are you using multicast or unicast? Multicast is configured by default and if your environment doesn't allow for multicast (Say on AWS or Azure, for example) you will need to switch to unicast.

Hi Dave,

The servers are hosted on prem, the cluster configuration being used is TCP_IP.

Two things that we frequently see are that the host-based firewall does not allow the TCP traffic through.  This requires a modification to the host-based firewall. Used the example on the page I linked above, you would need to allow inbound TCP:8088 from all nodes in the cluster on each node.  Also check SElinux if you are running on linux.  You should see the blocks in your system logs. I would recommend using tcpping or some other utility that allows you to ping using TCP vs ICMP in order to validate the ports are open and that TCP traffic is flowing.

Additionally, you need to configure all nodes for unicast and adjust the configuration file on each node so that each node knows about all others.  You will have odd behavior if some nodes don't know about others. I hope that helps.

Hi Dave, sorry for the late reply.

Apparently there was an unknown external resource that was blocking the connectivity between the nodes.

Not having full visibility into the infrastructure, we were also unaware of this communication.

Thank you very much for your interest and response.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events