In previous versions of JBoss EAP 6, it was found that `CoreGroupCommunicationService#handle` was mishandling exceptions, affecting caller of the class.
The class was found to be hiding exceptions and returning `null` values instead. This value could produce unexpected and unintended behaviors in callers.
In this release, the null response will be dealt with by the distributed lock manager, however the use of `CommandDispatcher` in future releases of the product will resolve the issue permanently.
org/jboss/as/clustering/impl/CoreGroupCommunicationService#handle catches and hides any internal exceptions, and just returns null instead.
This breaks callers of CoreGroupCommunicationService when they get a null value where it's not expected (after verifying that the response was not flagged as an exception)
It also catches an exception from the called method, and returns it as the return value, instead of just throwing it as an exception so it can be properly returned as an exception inside JGroups' RequestCorrelator.
Paul Ferraro <firstname.lastname@example.org> updated the status of jira WFLY-1351 to Closed
Paul Ferraro <email@example.com> made a comment on jira WFLY-1351
CoreGroupCommunicationService is obsolete. This issue does not apply to its replacement, CommandDispatcher.
Technically, this issue is still relevant to 6.2 and 6.3, as this class will continue to exist. However, the plan for EAP 6.3 is to drop usage of this object for locking web sessions.
Rather than change the API (which would be necessary to return the appropriate exception back to the caller), we'll handle the null response in the distributed lock manager.
Changed <literal></literal> tags in Doc Text to ticks (`) to fix Bug 1096865