As an JIRA Datacenter Administrator I want use default ehcache RMI port

XMLWordPrintable

    • 12
    • 18
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center

      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:

      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

      cluster.properties

      ...
      ehcache.object.port = 40011

            Assignee:
            Andriy Yakovlev [Atlassian]
            Reporter:
            Andriy Yakovlev [Atlassian]
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: