I'm setting up a JIRA Data Center in AWS and an issue rose up
We are using ehcache.listener.hostName = <node-hostname> on cluster.properties file, because RMI was throwing UnknownHostException without it.
When I've tried setting
ehcache.listener.hostname = <load-balancer-hostname>
RMI couldn't connect to Load Balancer on 40001 due to connection refused. Setting a listener rule in the ELB for port 40001 made no changes on outcome.
Anyone have experienced something similar?
Thanks in advance
If anyone encounters this issue, here is what we were missing...
Enable a Stickiness Policy on your listeners
Enable Stickiness with application cookie and set JSESSIONID as Cookie Name.
Hope this helps,
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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