JGroupsTransport.invokeRemotelyAsync with a filter returns null on
timeout
--------------------------------------------------------------------------
Key: ISPN-6384
URL:
https://issues.jboss.org/browse/ISPN-6384
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 8.2.0.Final, 9.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 8.2.1.Final, 9.0.0.Alpha1, 9.0.0.Final
{{JGroupsTransport.invokeRemotelyAsync()}} has a {{ResponseFilter}} parameter that was
traditionally used only with {{ResponseMode.GET_FIRST}}, for remote get commands. In that
particular case, returning a {{null}} when some of the nodes timed out and other nodes
returned invalid responses (i.e. {{null}}) was acceptable.
Since ISPN-4979, {{JGroupsTransport.invokeRemotelyAsync()}} is also used by
{{ClusterTopologyManagerImpl}}, with {{ResponseMode.GET_ALL}}. Here, however, returning a
{{null}} instead of throwing a {{TimeoutException}} is not acceptable.