jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: [jira] Closed: (JCR-335) Deadlock caused by versioning operations within transaction
Date Tue, 28 Mar 2006 19:57:19 GMT
Hi,

On 3/28/06, Alexandru Popescu <the.mindstorm.mailinglist@gmail.com> wrote:
> Sorry to ask: what is the status of this issue? I see it is closed, but fix
> version is set to 1.1.

The initial JCR-335 fix was included in the 1.0 branch early on, but
the issue was then reopened and another fix was made. Although the
latter fix is not too complex, it still is a bit risky (concurrent
locking operations are never easy) compared to the benefits,
especially since there are a number of other known issues about the
thread-safety of the versioning implementation. Thus I've decided not
to include the fix in the 1.0 release.

The fix will be in 1.1 and most probably also in 1.0.1 if there's
enough demand for a patch release containing this and other bug fixes.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Mime
View raw message