-
Suggestion
-
Resolution: Fixed
-
12
-
18
-
-
Problem Definition
See related ticket: JRASERVER-64974
JIRA Datacenter (JDC) uses Ehcache as caching technology, cache server which exposes available cache operations remotely through RMI. Ehcache requires two ports for it's network operations:
- port - a port in the range 1025 - 65536
- remoteObjectPort - the port number on which the remote objects bound in the registry receive calls. This defaults to a free port if not specified.
Currently in JDC (7.3+) you can specify:
- port (default = 40001, setting: ehcache.listener.port), see Cluster.properties file parameters
- remoteObjectPort (default = dynamic, setting: ehcache.object.port)
So by default remoteObjectPort is dynamically allocated and TCP ephemeral port is selected. So you need to open wide range of ports at firewall.
Suggested Solution
Set ehcache.object.port by default to 40011
Implemented
In the fixed version, it's required to open two ports for each node (see JRASERVER-68652)
- Ehcache port default 40001
- Object port default 40011
Workaround
Set ehcache.object.port manually
...
ehcache.object.port = 40011
- is related to
-
JRASERVER-64976 Include firewall configuration into JIRA DC docs
- Closed
-
JRASERVER-64974 Add the ability to customize the ehcache object port in Jira Data Center
- Closed
- relates to
-
JRASERVER-68652 Improve Jira DC documentation to explicitly mention Communication ports
- Gathering Interest