-
1. Re: Element stays locked after cluster node restart - Could not acquire lock
rvansa Nov 18, 2014 3:44 AM (in response to fille)5.3 is still quite an old version, given that now we have 7.0.1. Could you try with current version? (you will have to update your configuration file, regrettably)
-
2. Re: Element stays locked after cluster node restart - Could not acquire lock
fille Nov 18, 2014 4:02 AM (in response to rvansa)Yes, we will definitely be upgrading to ispn 7.x somewhere next year. In the meanwhile we will be running 5.3. And there is no guarantee that version 7 will fix this problem.
-
3. Re: Element stays locked after cluster node restart - Could not acquire lock
rvansa Nov 18, 2014 4:39 AM (in response to fille)1 of 1 people found this helpfulIt obviously looks like a bug. However, nobody will try to investigate/solve that in almost 2 years old version - if it is reproducible in new versions, it could get some attention and by the time you'll be upgrading to 7, there could be 7.0.x which will have the fix included.
-
4. Re: Element stays locked after cluster node restart - Could not acquire lock
fille Nov 18, 2014 5:37 AM (in response to rvansa)In fact, we were on 5.1 and due to this problem we tried to upgrade to 6.0.1. But this version was incompatible with our JVM setup. ISPN 5.3 did however contain a lot of fixes that were backmerged from 6.x and some of these fixes were really about a similar problem. ([ISPN-3736] Backport to 5.2.x for EAP 6.3 - JBoss Issue Tracker). So the hopes were high for this 5.3 version. But I see your point that we need to upgrade if we want this issue to be fixed. Thanks!
-
5. Re: Element stays locked after cluster node restart - Could not acquire lock
an1310 Nov 18, 2014 8:03 AM (in response to fille)The 5.2.x release has a lot of cases where you could end up with stale locks. I found and, with the team's help, fixed them. My submissions -- one which covers this exact case -- are in the 6.0.x and 7.0.x branches. However, if you're stuck on 5.2.x, I've backported them to my branch: an1310/infinispan at 5.2.0-BNI · GitHub
I wouldn't use that branch as-is, as it's written for my environment. However, this should help you along.