It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA DC Node: ehcache connection refused Edited

Sebastian Kouba Sep 01, 2017

I'm trying to start a second JIRA DC node but I get the following error on the second node (jira1):


[n.sf.ehcache.CacheManager] Cache com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizGroupCache.groupCacherequested bootstrap but a CacheException occured. Error bootstrapping from remote peer. Message was: Connection refused to host:; nested exception is: Connection timed out (Connection timed out)

and a bunch more connection refused / timeout messages.

According to my telnet test, port 40001 is open between the servers. This was run on the second node, jira1, where the error occurs.

telnet jira0 40001
Connected to jira0.

I've only set the node names in so everything else is default.

What other ports need to be open for DC to work? There is a mention in the documentation of "unrestricted access" between machines but I'm not sure that's going to happen in my case...

I've tried deleteing the plugin caches as per help article, no dice. The first node is running as intended.

Any ideas?



=> Solution

There is another port other than 40001 that needs to be opened. You can add this line to

ehcache.object.port = 40011

1 answer

1 accepted

0 votes
Answer accepted
Sebastian Kouba Sep 05, 2017

We've temporarily disabled all firewalls on the network. Now the nodes work.

Can anybody provide information as to which ports need to be acessible between machines? Looks like some ports in the 30000-50000 range.


Just found this in the documentation:

"Nodes must be configured to have unrestricted port access to each other"

Really? Just open the flood gates?

Sebastian Kouba Sep 05, 2017

Seems related to this after all:

Sebastian Kouba Sep 05, 2017 • edited

Very disappointing that for this "enterprise" product there is no documentation of some of the most basic setup steps, except hidden in some ticket to update the documentation...

Quote from the ticket linked above:

New variable: ehcache.object.port
Default port: 40011


Note that 40011 doesn't actually seem to be the default port. I had to set the port in before it worked as expected.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

334 views 0 9
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you