-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
9.5.0, 9.6.0, 9.7.0, 9.4.7
-
9.04
-
6
-
Severity 2 - Major
-
5
-
-
Issue Summary
With JSM 5.5 log4j v2 causes houndreds of WARN logs for any action that triggers indexing on issues. (edit/comment etc).
The logs state that issue should have a version by now. This is misleading as all issues have versions.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Install JSM 5.5 or later
- Create a JSM Project and comment
Expected Results
No WARN messages for the index operation happens if issue has a version.
Actual Results
Issue indexer thread throws WARN messages multiple times for every edit
2023-03-10 15:45:22,450+0000 SdSerialisedOffThreadProcessor:thread-4 WARN admin [c.a.j.issue.index.DefaultIssueIndexer] ISSUE with id=10201 should have a version by now 2023-03-10 15:45:22,644+0000 SdSerialisedOffThreadProcessor:thread-4 WARN admin [c.a.j.issue.index.DefaultIssueIndexer] ISSUE with id=10201 should have a version by now
How to validate if all issues have versions?
We are aware of the issue causing JSM code to produce misleading logs.
In case the log is coming from threads:
- PsmqAsyncExecutors-job
- SdSerialisedOffThreadProcessor
- http-nio threads from greenhopper rest endpoints
It is very likely that the log is misleading and in fact all issues have an issue version.
To further validate you can run a following query:
select count(*)
from jiraissue
left join issue_version on jiraissue.id = issue_version.issue_id
where issue_version.issue_id is null;
The correct result should be 0. In case it is more than 0 Jira is in inconsistent state and requires further diagnosis.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
![[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.](https://bulldog.internal.atlassian.com/images/icons/issuetypes/story.svg "[JIRA Server (Bulldog)] Story - Created by Jira Software - do not edit or delete. Issue type for a user story.")
DELTA-1511
You do not have permission to view this issue
[JRASERVER-75166] WARNINGS in JSM log - ISSUE with id=xxxxxx should have a version by now although all issues have versions
Can you please reopen this ticket or link a new one? We still see this in 9.12.10.
Still seeing this in 9.4.17, is it correct to assume, that this fixes the cause, but not the damage already done in the DB?
Ours returns to SQL in description value of 12 matches.
.
//Tomas
| Remote Link | New: This issue links to "Page (Confluence)" [ 835497 ] |
| Introduced in Version | Original: 9.05 | New: 9.04 |
| Affects Version/s | New: 9.4.7 [ 105092 ] |
| Fix Version/s | New: 9.4.11 [ 105823 ] |
| Current Status |
Original:
{panel:title=Atlassian Update – 26 April 2023|borderStyle=solid|borderColor=#deebff | titleBGColor=#deebff | bgColor=#deebff}
Dear Customers, We're happy to announce that this issue will be fixed in 9.9.0 release. We are introducing changes that ensure no misleading logs are produced. Warning is now expected to be displayed only in case of an actually missing version. Best regards, Krzysztof Krysiak Jira Developer {panel} |
New:
{panel:title=Atlassian Update – 20 September 2023|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
Dear Customers, We're happy to announce that the fix to this issue will be backported to the Jira 9.4.11 LTS version, which is planned to be released in October 2023. Best regards, Daria Misiowiec Software Engineer, Jira DC {panel} |
I'm currently updating to the new version 9.12.15 that was released today
The problem is still there.
The atlassian-jira.log file is filled with this and jira indexing takes ages.
This is very frustrating and unexpectedly Jira update time is unnecessarily extended