Re: [jgroups-users] RpcDispatcher does not invoke remote method

The code provided can be used to reproduce the issue mentioned. All is well
until a byte buffer of size 65353 is transferred using fork channel.  
However, increasing the size by even 1 byte produces the issue (RPC call not
invoked). Probably there is some limitation which uses 64k chunks by default
(65536 - 65353 = 183). I suppose the deficit 183 bytes are used up by the
Message metadata. I initially had this issue when I sent 1MB chunks via RPC.
The main channel works well irrespective of the buffer size. If fork
channels use the same communication mechanism internally I am wondering why
this won't work for fork channels. This cannot be the bundling size since
setting  also gives the same result. The jgroups manual nor the 
https://github.com/belaban/JGroups/blob/master/doc/design/FORK.txt
<https://github.com/belaban/JGroups/blob/master/doc/design/FORK.txt>  
provides any info relating of size limitations while using Fork channels for
transport. 
I am using JGroups 4.0.2. The protocol stack used is




--
View this message in context: http://jgroups.1086181.n5.nabble.com/jgroups-users-RpcDispatcher-does-not-invoke-remote-method-tp11333p11339.html
Sent from the JGroups - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot