How do I check if we have a custom log4j configuration?

[Ulf Johansson]

Hi, reaching out for help!
I'm about to upgrade from JSW 9.3 to 9.5 and JSM 5.3 to 5.5 and the notes regarding breaking change of the upgrade to log4j2

How do I check if we have a custom log4j configuration as mentioned in the upgrade notes?
Seems like we using file log4j.properties now.
This param do I see in the file:

log4j.appender.filelog=com.atlassian.jira.logging.JiraHomeAppender
log4j.appender.filelog.File=atlassian-jira.log

And inside in Jira/Logging and profiling this is shown:

[Nic Brough -Adaptavist- · Accepted solution]

There are a few things you can look at.

• The easiest and quickest; All the files that are part of the installation, including the log4j.properties file will have a very similar date and time stamp.  If the date/time are significantly different from other files in the directory, it has been amended (not a 100% guarantee - it may have been amended, and then changed back to the installed version)
• Nip into Admin -> System -> System support -> System info.  There is usually a section on "modified files".  It's a bit more reliable than date/time, it's comparing a couple of hashes.  But I don't know when it checks for changed files, startup, overnight, backup, or some other cycle, so I would recommend only using this one after Confluence has been up and running for at least a whole day.
• If you are using the installer to do the upgrade, it will list the modified files before asking you if you want to continue the upgrade, but it's doing it based on the two above.
• The most reliable method is to install a new confluence of the same version (not the new one), only to the point where all the installation files are in place, and then use a "diff" to compare the clean install version of the file with the one on your server.

[Ulf Johansson]

I niped in to modified files.
All good then I assume.

Modified Files [Installation Type: Standalone] jira-application.properties