Re: [jgroups-users] RPC Timing Out

If the RPC can never deadlock, why don't you set a timeout of 0 (which 
disables timeouts)?
Eventually the data will be received and the call will terminate. A 
crash of the sender or receiver will cause the call to terminate; the 
failure detection protocol(s) will do this.

Perhaps I don't understand what you're trying to do; in that case, a 
unit tests will help... :-)

On 14/06/16 23:47, Questions/problems related to using JGroups wrote:
> Hello all,
>
> We have some RPCs that return fairly significant amounts of data.  As a
> result, those calls can be prone to time out.  In order to combat that
> issue we have, on 3.0.2, added code that sends messages up the stack to
> keep the RPC from timing out.  We could reimplement that on 3.6.9, but
> before we do so we wanted to make sure there is not a “more standard”
> way to solve the issue.
>
> Note that we do not want to set an “extra-long” timeout, as failures do
> occur.  Rather we would want to be notified as soon as reasonable of
> said failure.  Ideally we would set a fairly short timeout – perhaps 5
> seconds – and as long as the host continues to receive FRAGments of the
> response we could bubble a keep alive up the stack.
>
> Thoughts and advice are appreciated.
>
> Regards,
>
> Neal

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381