Issue Details (XML | Word | Printable)

Key: JRA-7040
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Brian Nguyen [OLD]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Concurrency problem when running Workflow Current Step Check

Created: 16/Jun/05 08:47 PM   Updated: 11/Feb/08 01:47 AM
Component/s: Backend / Domain Model, Workflow
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Anton Mazkovoi [Atlassian] and Brian Nguyen [OLD]
Since last comment: 2 years, 11 weeks, 3 days ago
Labels:


 Description  « Hide
The integrity checker loads all the issues into memory. So if while running the Workflow Current Step Check another user executes a transition on an issue, an inconsistency is caught by Jira between the current step table and the issues in memory. It then tries to correct the percieved error which means the issue now has the wrong step for the status.

This is best fixed by implementing Joins so all required date is retrieved at the same time.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Anton Mazkovoi [Atlassian] added a comment - 25/Jul/06 12:52 AM
The situation here has improved. The integrity checker goes through issues one by one, and does not load them all into memory. There is a small chance that if the issue is progressed through workflow while the integrity checker is working on that one issue, the integrity checker could still detect "a problem".

The chance of this happening is very small.