Instance health tab is showing no data with null pointer exception in logs

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.



Instance health tab in Support Tools is showing no information or "The contents of this tab is loading"


The issue is observed after the upgrade to 7.13.x but it can occur on any version.


Checking the logs we can see Null pointer exceptions like this one:

2021-10-11 10:18:44,379 ERROR [https-jsse-nio-8443-exec-1704] [ContainerBase.[Standalone].[localhost].[/]] log Unhandled exception occurred whilst decorating page
 -- referer: https://<base-url>/plugins/servlet/troubleshooting/view/ | url: /plugins/servlet/troubleshooting/view/atst-detect-issues/view | traceId: 92e3fe287b1e8463 | userName: <user>
	at java.base/java.util.Arrays.sort(Unknown Source)
	at com.atlassian.troubleshooting.confluence.ConfluenceApplicationInfo.addUpgradeRecoveryFileNames(
	at com.atlassian.troubleshooting.confluence.ConfluenceApplicationInfo.internalLoadProperties(
	at com.atlassian.troubleshooting.stp.salext.AbstractSupportApplicationInfo.lambda$loadProperties$0(
	at java.base/ Source)
	at com.atlassian.util.concurrent.ConcurrentOperationMapImpl$CallerRunsFuture.get(
	at com.atlassian.util.concurrent.ConcurrentOperationMapImpl.runOperation(
	at com.atlassian.troubleshooting.stp.salext.AbstractSupportApplicationInfo.loadProperties(
	at com.atlassian.troubleshooting.stp.action.impl.DetectIssuesAction.prepare(
	at com.atlassian.troubleshooting.stp.servlet.SupportToolsViewServlet.displayResults(
	at com.atlassian.troubleshooting.stp.servlet.SupportToolsViewServlet.doGet(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(


This issue can occur when Confluence (or any application) is started as a root user. The process will create files that have either incorrect permissions or file ownership. In this particular case, we should check permissions and ownership of these locations:

  •  <confluence-shared-home>
  • <confluence-shared-home>/recovery


Check if Confluence is using a different user than confluence - user.

ps aux | grep confluence

Apply correct Confluence Linux permissions to both locations <confluence-shared-home> and <confluence-shared-home>/recovery and then restart Confluence.

Last modified on Oct 13, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.