-
Bug
-
Resolution: Fixed
-
Low
-
4.1.0
-
3
-
Severity 2 - Major
-
1
-
Summary
JSD 4.1 logs are flooded with SdOffThreadEventJobRunner INFO messages
As a result, built in JIRA log analyzer falsely detects that JIRA is affected by this issue:
https://jira.atlassian.com/browse/JSDSERVER-5736
In one customer's environment the message count is over 18K+
How to Replicate
- Deploy brand new JSD 4.1 and create a test JSD project with sample data
- In that project add a couple more automation rules (might be optional)
- Perform a few activities on JIRA tickets (like add a comment, change the assignee etc) while monitoring (tail -f) atlassian-jira.log - see how SdOffThreadEventJobRunner logs the following messages:
2019-05-20 11:19:42,657 SdOffThreadEventJobRunner:thread-2 INFO sergeos 679x128x1 stz5eq 0:0:0:0:0:0:0:1 /rest/api/2/issue/10037/comment [c.a.jira.index.MonitoringIndexWriter] [lucene-stats] flush stats: snapshotCount=5, totalCount=5, periodSec=0, flushIntervalMillis=41, indexDirectory=null, indexWriterId=com.atlassian.jira.index.MonitoringIndexWriter@6bc25ef1, indexDirectoryId=RAMDirectory@95c9a34 lockFactory=org.apache.lucene.store.SingleInstanceLockFactory@db81932
Workaround
Add "com.atlassian.jira.index.MonitoringIndexWriter" custom package to logging and profiling in JIRA and set the debug log level to ERROR.
That is until JIRA is restarted. To get the setting permanent, it'll need to be added to log4.properties file as per this article:
https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html
- is resolved by
-
-
- Closed
-
- mentioned in
-
Page Loading...