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) java.lang.NullPointerException at org.jboss.as.clustering.lock.AbstractClusterLockSupport.lock(AbstractClusterLockSupport.java:157) 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 <paul.ferraro> updated the status of jira WFLY-1351 to Closed
Paul Ferraro <paul.ferraro> 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.
https://github.com/jbossas/jboss-eap/pull/750
6.3.0.DR0 verified.
Changed <literal></literal> tags in Doc Text to ticks (`) to fix Bug 1096865