[#SCAR-8] LockObtainFailedException while trying to acquire Lucene locks.

Scarlet - Clustering for Jira

LockObtainFailedException while trying to acquire Lucene locks.

Created: 10/Mar/08 04:45 AM Updated: 11/Mar/08 05:28 AM

Component/s:

Lucene Indexes

Affects Version/s:

1.0RC1

Fix Version/s:

1.0RC2

Time Tracking:

Not Specified

Issue Links:

Cause

This issue caused:

~~SCAR-7~~ writelock, threaddump, lock timeout... while submitting JIRA issues

Labels:

Description

« Hide

Jira's ConcurrentLuceneConnection needs to be properly protected by cluster-wide locks in order to avoid LockObtainFailedException while trying to acquire Lucene locks.

All

Comments

Work Log

Change History

FishEye

Crucible

Builds

Sort Order:

[ Permlink | « Hide ]

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

Fixed by applying write-level named locks to ConcurrentLuceneConnection write methods.