[
https://issues.jboss.org/browse/ISPN-6795?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-6795:
------------------------------------
For the record, remote gets were never intended to report exceptions from the other side.
The idea was that if there's an exception from one target, we'd still want to wait
for a response from the others, and if none of the targets return a valid response,
`invokeRemotely` would throw a `RpcException`. So this is really an enhancement request,
not a bug.
ClusteredGetResponseValidityFilter swallows exceptions
------------------------------------------------------
Key: ISPN-6795
URL:
https://issues.jboss.org/browse/ISPN-6795
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.0.0.Alpha2
Reporter: Radim Vansa
Priority: Minor
ClusteredGetValidityFilter does not accept exceptional responses. Therefore, if
there's a exception on the remote side when executing ClusteredGetCommand, it's
swallowed and TimeoutException is thrown instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)