https://issues.jboss.org/browse/JGRP-1958
PR sent https://github.com/belaban/JGroups/pull/343
Note that there is no upstream required, because the backported commit [1] https://github.com/belaban/JGroups/commit/03d7c93145f6a9314c2380f5ad66bdc8ec4209f0 is a part of both JGroups 3.6.10 (in EAP 7.0) and 3.6.12 (in EAP 7.1)
Verified with EAP 6.4.16.CP.CR1
i also thought that it would be WARN or even lower since as far as i understand it has no adverse effect , and its just a result of the shutdown process. Is the correct?
I think so. In that case I have to reopen this BZ. Because the fix is just particular. The stack trace is not shown. Message is SEVERE but should be WARN or lower.
I interpreted the sparse description if this bug as "backport the fix for JGRP-1958" which I did. If you are not content with the original fix https://github.com/belaban/JGroups/commit/03d7c93145f6a9314c2380f5ad66bdc8ec4209f0 then apparently, my interpretation was wrong :) This being a backport of an upstream fix that was delivered ~18 month ago, I do not think reopening this bug can bring anything useful. I simply cannot put a new behavior to a maintenance branch that is not present in master. That would require a new JGroups Jira. I propose that (1) Jirka accepts this as a correct backport of an imperfect upstream fix and (2) Shay files a new BZ with proper acceptance criteria that will result in creating a new upstream Jira that will request the change in the log level in master and all relevant maintenance branches. WDYT?
Verified because backport was successfuly done.
ok we can close this , I opened : https://bugzilla.redhat.com/show_bug.cgi?id=1463387
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.