You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by John Langley <la...@gmail.com> on 2011/02/08 17:15:51 UTC
jcr 2881 Deadlock on version operations in a clustered environment
I believe I'm seeing this in 2.1.3 as well.
What's the likelihood of the fix being ported to the 2.1 branch?
Thanks in advance for commenting
Re: jcr 2881 Deadlock on version operations in a clustered environment
Posted by John Langley <la...@gmail.com>.
Thank you VERY MUCH Jukka. If you need early testing let me know.
-- Langley
On Wed, Feb 9, 2011 at 4:07 AM, Jukka Zitting <jz...@adobe.com> wrote:
> Hi,
>
>
> On 02/08/2011 05:15 PM, John Langley wrote:
>
>> I believe I'm seeing this in 2.1.3 as well.
>> What's the likelihood of the fix being ported to the 2.1 branch?
>>
>
> Much higher now that someone asked for it. :-)
>
> I'll see to it that the fix gets included in the next 2.1.x release.
>
> --
> Jukka Zitting
>
Re: jcr 2881 Deadlock on version operations in a clustered environment
Posted by John Langley <la...@gmail.com>.
You Rock!
I'll try it today and also scope out the resource/jdbc connection loss
issue.
-- Langley
On Fri, Feb 11, 2011 at 9:33 AM, Jukka Zitting <jz...@adobe.com> wrote:
> Hi,
>
>
> On 02/10/2011 11:26 PM, John Langley wrote:
>
>> I looked at "back porting" the 2881 to 2.1.3 locally. But it appears
>> that just using the change set from 2881 and "pretty blindly copying
>> it" into the 2.1.3 code base doesn't work, apparently there are other
>> changes needed too.
>>
>
> Yes, the JCR-2881 change depends on earlier changes in JCR-2865. I merged
> both changes to the 2.1 branch in revision 1069811.
>
> --
> Jukka Zitting
>
Re: jcr 2881 Deadlock on version operations in a clustered environment
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 02/10/2011 11:26 PM, John Langley wrote:
> I looked at "back porting" the 2881 to 2.1.3 locally. But it appears
> that just using the change set from 2881 and "pretty blindly copying
> it" into the 2.1.3 code base doesn't work, apparently there are other
> changes needed too.
Yes, the JCR-2881 change depends on earlier changes in JCR-2865. I
merged both changes to the 2.1 branch in revision 1069811.
--
Jukka Zitting
Re: jcr 2881 Deadlock on version operations in a clustered environment
Posted by John Langley <la...@gmail.com>.
Jukka,
I looked at "back porting" the 2881 to 2.1.3 locally. But it appears that
just using the change set from 2881 and "pretty blindly copying it" into the
2.1.3 code base doesn't work, apparently there are other changes needed too.
Does that sound consistent with your expectations?
Thanks in advance,
-- John Langley
On Wed, Feb 9, 2011 at 4:07 AM, Jukka Zitting <jz...@adobe.com> wrote:
> Hi,
>
>
> On 02/08/2011 05:15 PM, John Langley wrote:
>
>> I believe I'm seeing this in 2.1.3 as well.
>> What's the likelihood of the fix being ported to the 2.1 branch?
>>
>
> Much higher now that someone asked for it. :-)
>
> I'll see to it that the fix gets included in the next 2.1.x release.
>
> --
> Jukka Zitting
>
Re: jcr 2881 Deadlock on version operations in a clustered environment
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 02/08/2011 05:15 PM, John Langley wrote:
> I believe I'm seeing this in 2.1.3 as well.
> What's the likelihood of the fix being ported to the 2.1 branch?
Much higher now that someone asked for it. :-)
I'll see to it that the fix gets included in the next 2.1.x release.
--
Jukka Zitting