Closed GoogleCodeExporter closed 9 years ago
Can you make the change from r409 and see if it fixes this issue?
I need to get version 6.5 out at some point.
Original comment by widdis@gmail.com
on 21 Nov 2011 at 1:41
Er, disregard comment 1, or at least clarify it below.
The message given indicates that the member without access is still a member of
the jgroup. You should be able to remove them from the jgroup (after applying
the code change in r409) and then the job reassignment should work. So I'm not
sure this is a new issue as just a followon capability lost if you haven't
applied the Issue 160 fix.
Original comment by widdis@gmail.com
on 21 Nov 2011 at 1:58
Confirmed, removing them from the jgroup fixed this. Probably okay to close
this out; the error message really is about as clear as it can be and I should
have understood what it meant.
Original comment by lasht...@gmail.com
on 21 Nov 2011 at 8:53
Not your fault this next release is so slow in coming. I hate do do a release
for only one line of code though! :)
Original comment by widdis@gmail.com
on 22 Nov 2011 at 6:44
Original issue reported on code.google.com by
lasht...@gmail.com
on 18 Nov 2011 at 7:05