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,
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot