Jira Boards and Tickets are loading slowly
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 knowledge base article describes a scenario where enabling SQL logging can lead to slow or failure loading boards and tickets.
Environment
8.20.x
Diagnosis
From thread-dump, we can observe that SQL logging is enabled and all incoming http request are blocked on log4j api to log SQL logging.
The SQL logs will be in
<JIRA HOME>/log/atlassian-jira-sql.log.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
"https-jsse-nio2-8443-exec-2207 url: /rest/issueNav/1/issueTable; user: 9846609" #394231 daemon prio=5 os_prio=0 tid=0x00007fee90100800 nid=0x6055 waiting for monitor entry [0x00007feaeb0f5000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:231)
- locked <0x0000000440434f98> (a org.apache.log4j.RollingFileAppender)
at com.atlassian.jira.logging.JiraHomeAppender.doAppend(JiraHomeAppender.java:206)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:69)
at org.apache.log4j.Category.callAppenders(Category.java:219)
at org.apache.log4j.Category.forcedLog(Category.java:402)
at org.apache.log4j.Category.log(Category.java:869)
at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:305)
at com.atlassian.jira.ofbiz.LoggingSQLInterceptor.onConnectionReplaced(LoggingSQLInterceptor.java:39)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.lambda$onConnectionReplaced$1(ChainedSQLInterceptor.java:70)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor$$Lambda$138/1229795498.accept(Unknown Source)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.forEach(ChainedSQLInterceptor.java:93)
at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.onConnectionReplaced(ChainedSQLInterceptor.java:69)
at org.ofbiz.core.entity.jdbc.interceptors.connection.SafeDelegatingSqlConnectionInterceptor.onConnectionReplaced(SafeDelegatingSqlConnectionInterceptor.java:39)
at org.ofbiz.core.entity.jdbc.interceptors.connection.ConnectionTracker$DelegatingConnectionImpl.close(ConnectionTracker.java:86)
at com.atlassian.jira.ofbiz.sql.ConnectionWrapper.close(ConnectionWrapper.java:77)
at com.atlassian.jira.diagnostic.connection.DiagnosticConnection.close(DiagnosticConnection.java:91)
at org.ofbiz.core.entity.jdbc.SQLProcessor.closeConnection(SQLProcessor.java:287)
at org.ofbiz.core.entity.jdbc.SQLProcessor.close(SQLProcessor.java:242)
at org.ofbiz.core.entity.EntityListIterator.close(EntityListIterator.java:165)
"https-jsse-nio2-8443-exec-2205 url: /rest/greenhopper/1.0/xboard/issue/details/details; user: 5591427" #394029 daemon prio=5 os_prio=0 tid=0x00007fee202d4000 nid=0x49d7 waiting for monitor entry [0x00007fed60d7a000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:231)
- waiting to lock <0x0000000440434f98> (a org.apache.log4j.RollingFileAppender)
at com.atlassian.jira.logging.JiraHomeAppender.doAppend(JiraHomeAppender.java:206)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:69)
at org.apache.log4j.Category.callAppenders(Category.java:219)
at org.apache.log4j.Category.forcedLog(Category.java:402)
at org.apache.log4j.Category.log(Category.java:869)
at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:305) Solution
We should not enable SQL logging in production environment environment.
Disable SQL logging as per article Enable SQL query logging in Jira server. If SQL logging is enabled we should see Disable button, for reference check red color rectangular box in following image. Click on Disable button.
Was this helpful?