[#SCAR-9] DefaultProjectManager generates duplicated issue keys on racing conditions.

Scarlet - Clustering for Jira

DefaultProjectManager generates duplicated issue keys on racing conditions.

Created: 10/Mar/08 04:52 AM Updated: 07/May/08 03:35 AM

Component/s:

Core Components

Affects Version/s:

1.0RC1

Fix Version/s:

1.0RC2

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

~~SCAR-14~~ Optimize DefaultProjectManager issue key generation

Labels:

Description

« Hide

DefaultProjectManager needs to be properly protected by cluster-wide locks because it currently generates duplicated issue keys on racing conditions.
However, this is a minor bug because the DefaultProjectManager keeps regenerating the key until it finds a unique one.

All

Comments

Work Log

Change History

FishEye

Crucible

Builds

Sort Order:

[ Permlink | « Hide ]

Sergio Bossa added a comment - 11/Mar/08 05:20 AM

The log message about an existing key found will be still displayed, but the key will be correctly incremented even under heavy concurrency and race conditions.