Confluence diagnostics: Thread memory allocation rate exceeded limit
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This diagnostic alert is disabled by default, as it may have a performance impact on your site. Our support team may ask you to enable this alert when troubleshooting a specific problem.
This diagnostic alert warns you when Confluence detects that the memory allocation to a particular thread, during a set monitoring period, is high, and likely to affect the performance of the application.
The following appears in the application log:
1
INFO ; JVM ; JVM-1001 ; Thread memory allocation rate exceeded limit ; not-detected ; ; ; {...}Solution
To resolve this issue
There's no action required for this alert. However, this information may be helpful when investigating performance issues.
What will happen if I ignore this alert?
This alert is for information only. There's no direct action required.
Can I change the threshold?
Yes, you can change the threshold of this alert using the following system properties:
diagnostics.jvm.memory.allocation.rate.percent
diagnostics.jvm.memory.allocation.monitoring.period.secs
diagnostics.jvm.memory.check.period.secs
See Configuring System Properties for more information on setting system properties.
Was this helpful?