Re: [jgroups-users] RPC Timing Out

On 15/06/16 02:05, Questions/problems related to using JGroups wrote:
> All,
>
> Apologies for following up to my own inquiry.. one more point/question:
> It appears that only one RPC can be responded to at a time.
>
> For example, if we call GiantResponseRPC from host A to host B and from
> another thread call SmallResponseRPC to the same host, we will not
> receive a response to the latter until the response to the former is
> received.  Is that expected?

Yes, as messages are by default sent in per-sender FIFO order. If 
GiantResponseRPC generates messages A[4,5,7] and SmallResponseRPC 
A[3,6,8], then GiantResponseRPC will be received first, as soon as B has 
received message A7, and SmallResponseRPC second.

You can change this by marking the messages as OOB, e.g. set the OOB 
message flag in the RequestOptions passed to the RPC.

> Regards,
>
> Neal
>
> *From:* Questions/problems related to using JGroups
> [mailto:[email protected]]
> *Sent:* Tuesday, June 14, 2016 2:47 PM
> *To:* [email protected]
> *Subject:* [jgroups-users] RPC Timing Out
>
> 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
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
>
> _______________________________________________
> javagroups-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/javagroups-users
>

-- 
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