Description of problem: Tracking bug for JDG 6.6 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This has been fixed upstream, so the following commit just needs to be cherry picked: https://github.com/belaban/JGroups/commit/a95a3e2e3f2707d41388bf00e2f9bf6ec37bf262
(In reply to Alan Field from comment #2) > This has been fixed upstream, so the following commit just needs to be > cherry picked: > > https://github.com/belaban/JGroups/commit/ > a95a3e2e3f2707d41388bf00e2f9bf6ec37bf262 Actually, the previous commit did not fix the issue, but this one will: https://github.com/alanfx/JGroups/commit/78ce57a3f4b7acfb2ad9c9fdcf0d1a45630ee8b7
(In reply to Alan Field from comment #3) > (In reply to Alan Field from comment #2) > > This has been fixed upstream, so the following commit just needs to be > > cherry picked: > > > > https://github.com/belaban/JGroups/commit/ > > a95a3e2e3f2707d41388bf00e2f9bf6ec37bf262 > > Actually, the previous commit did not fix the issue, but this one will: > > https://github.com/alanfx/JGroups/commit/ > 78ce57a3f4b7acfb2ad9c9fdcf0d1a45630ee8b7 This is the ultimate fix for this issue: (I mean it this time!) https://github.com/belaban/JGroups/commit/983fc49edc0350c081158bea4a534bdb4e70ed29
Vaclav Dedik <vdedik> updated the status of jira JDG-85 to Resolved
Fix needs to be cherry-picked into JDG
Fixed: https://github.com/infinispan/jdg/commit/6c5b9c1e196f17d102c198870124a31f1c30b3ca
Verified with JDG 6.6.1 ER1