Minimal connectivity between nodes in JIRA Datacenter

This question is in reference to Atlassian Documentation: Installing JIRA Data Center


I was configuring JIRA in Datacenter mode on a cloud infrastructure and I couldn't find in the existing Atlassian answers or JIRA Datacenter documentation pages the minimal connectivity required between 2 nodes. The only info I found was that they "must be located in the same data center".

Question : what is the minimal connectivity required between nodes for JIRA Datacenter ?

Thanks in advance for your help


2 answers

What do you mean by minimal connectivity here? Whatever I've read in is pretty straight forward for me. Maybe you can explain more on what you need?


I have several nodes on the same datacenter, but by default they are totally separated one from each other and for each I need to specifically grant them access. 

  • Which ports/port ranges need to be allowed and for which protocols ?
  • Is there any use of multicast ?

I followed the documentation provided, but it does not specify enough the minimal requirements for the "connectivity".


Thanks in advance for your help,


The key point in the data center model here is the step #2, there's where the magic happens. No ports and protocols needed to be configured.

2. Set up the JIRA file storage location on shared storage

Thanks for your answer.

This is the error I got on the node that does not start (the other node is correctly starting with the licence and it connects correctly to the NFS & DB). Both are on AWS, on the same region, and on the same "Security Group".

2016-03-17 16:49:30,833 Caesium-1-4 ERROR ServiceRunner     [n.s.ehcache.distribution.RMISynchronousCacheReplicator] Exception on replication of putNotification. Connection refused to host: <IP node 2>; nested exception is: Connection timed out. Continuing...
java.rmi.ConnectException: Connection refused to host: <IP node 2>; nested exception is: Connection timed out
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(
    at sun.rmi.transport.tcp.TCPChannel.createConnection(
    at sun.rmi.transport.tcp.TCPChannel.newConnection(
    at sun.rmi.server.UnicastRef.invoke(
    at net.sf.ehcache.distribution.RMICachePeer_Stub.put(Unknown Source)
    at net.sf.ehcache.distribution.RMISynchronousCacheReplicator.replicatePutNotification(
    at net.sf.ehcache.distribution.RMISynchronousCacheReplicator.notifyElementUpdated(
    at net.sf.ehcache.event.RegisteredEventListeners.internalNotifyElementUpdated(
    at net.sf.ehcache.event.RegisteredEventListeners.notifyElementUpdated(
    at net.sf.ehcache.Cache.notifyPutInternalListeners(
    at net.sf.ehcache.Cache.putInternal(
    at net.sf.ehcache.Cache.put(
    at net.sf.ehcache.Cache.put(
    at com.atlassian.cache.ehcache.DelegatingCache.put(
    at com.atlassian.jira.plugins.healthcheck.service.HeartBeatService.propagateHeartBeat(
    at com.atlassian.jira.plugins.healthcheck.scheduler.impl.HealthCheckSchedulerImpl.runJob(
    at com.atlassian.scheduler.core.JobLauncher.runJob(
    at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(
    at com.atlassian.scheduler.core.JobLauncher.launch(
    at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(
    at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(
    at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(
    at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(
    at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(
    at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(
    at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(
Caused by: Connection timed out
    at Method)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(
    at net.sf.ehcache.distribution.ConfigurableRMIClientSocketFactory.createSocket(
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(
    ... 27 more

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

216 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you