As of 5.6 when we implemented G1GC as the default, in setenv.sh/setenv.bat, the default environment variable for JVM parameters has changed to CATALINA_OPTS, instead of JAVA_OPTS.

      This has the potential to cause confusion for customers:

      • If both exist and specify different parameters, which will be effective?
      • Customers may change one and not the other, and expect their changes to be picked up. This can greatly increase troubleshooting time
      • Documentation may reference one or the other and customers may have difficulty implementing advised changes, and need to contact Support (friction)

      For Support:

      • We now have to update documentation to give different advice based on versions, eg here
      • Support engineers need to know that this changed, so we can advise customers of the correct method depending on their version

        1. 56-setenv.sh
          1 kB
        2. 57-setenv.sh
          1 kB

            [CONFSERVER-36011] JAVA_OPTS has changed to CATALINA_OPTS

            Atlassian Update - 10 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Confluence Data Center

            George Varghese added a comment - Atlassian Update - 10 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Confluence Data Center

            I just gave confusing directions to the IT department as I was not aware of the change.

            Philipp Salzgeber added a comment - I just gave confusing directions to the IT department as I was not aware of the change.

            Not only confuse customers, but Atlassian support staff (see CSP-160331).
            Is the change documented in Atlassian documentation anywhere?

            Kevin Lange added a comment - Not only confuse customers, but Atlassian support staff (see CSP-160331). Is the change documented in Atlassian documentation anywhere?

              Unassigned Unassigned
              dunterwurzacher Denise Unterwurzacher [Atlassian] (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: