Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-92709

Confluence setup overwrites Docker environment values in confluence.cfg.xml

XMLWordPrintable

      Issue Summary

      During the Confluence setup, when selecting the DB, the confluence.cfg.xml is updated and replacing the value of hibernate.hikari.maximumPoolSize from the one added as ATL_DB_POOLMAXSIZE to a default one.
      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Create Confluence Docker container with environment variable `ATL_DB_POOLMAXSIZE`=`200`

      2. Start Confluence container

      3. Confirm that the value of `hibernate.hikari.maximumPoolSize` is `200`

      4. Select "Non-clustered" option from the "Chose your deployment type" page

      5. Observe that the value of `hibernate.hikari.maximumPoolSize` has been changed to `60`

      Expected Results

      Everytime a container is created or rebooted, to maintain the specified value confluence.cfg.xml

      Actual Results

      The container is created with a ATL_DB_POOLMAXSIZE, but after the DB setup in the browser, it changes.

      Attached is gif from our customer showing the behaviour:

      Workaround

      Edit the confluence.cfg.xml manually in the container.

            [CONFSERVER-92709] Confluence setup overwrites Docker environment values in confluence.cfg.xml

            There are no comments yet on this issue.

              Unassigned Unassigned
              a10ada9f39c1 betto
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: