Issue Summary

When following the steps in our Encrypt passwords in server.xml article, Jira will stop writing to a number of log files in the "<Jira_home>/log" location. Notably, the files below:

• "atlassian-jira.log"
• "atlassian-jira-app-monitoring.log"
• "atlassian-jira-ipd-monitoring.log"
• "atlassian-jira-migration.log"
• "atlassian-jira-outgoing-mail.log"
• "atlassian-jira-perf.log"
• "atlassian-jira-security.log"
• "atlassian-jira-stats.log"

There may also be other files impacted which are not listed here.
Note: this can be replicated easily in a brand new environment "out-of-the-box" where the "log4j2.xml" has not been modified at all.

Steps to Reproduce

1. Create a brand new Jira node with a working SSL Tomcat connector. Only needs to be one server, clustering is not required.
2. Follow the steps in our Encrypt passwords in server.xml to encrypt the passwords in the "server.xml" file
3. Start Jira

Expected Results

Jira should start-up and all logs should be written to as normal.

Actual Results

The log files in the "<Jira_home>/log" location listed above are not written to with new data.

Workaround

1.Stop Jira
2.Remove the old files(atlassian-secrets-store-3.2.8.jar & atlassian-secrets-api-3.2.8.jar) from <jira-install>/lib
3.Copy atlassian-secrets-store-3.2.9.jar & atlassian-secrets-api-3.2.9.jar from <jira-install>/atlassian-jira/WEB-INF/lib to <jira-install>/lib
3. Restart Jira.