Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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 now.
This param do I see in the file:



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

1 answer

0 votes

There are a few things you can look at.

  • The easiest and quickest; All the files that are part of the installation, including the 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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events