Strange behaviour with netty in .net (using ikvm)

["Trustin Lee (이희승)"]

Hi Leandro,

If operationComplete() has been called with successful future (i.e.
future.isSuccess() == true), it means SocketChannel.write() has been
succeeded without a problem.  No additional action is required to make
sure the write is successful.

If the peer really did not receive anything, I suspect a problem in the
peer (client?).  You could use a packet analyzer like WireShark to make
sure that there is no traffic - the peer might simply not be reading the
data.

HTH,
Trustin

Leandro Cruz wrote:
> Hi all.
> 
> We switched from mina to netty lately. We wrote a small client/server app
> that fragments binary data to send back and forth.
> When running from java the process seems to work pretty smoothly. But when
> we compile it to .net using ikvm the write queue seems jammed.
> 
> In our code we call channel.write multiple times and
> our ChannelFutureListener.operationComplete() is always successful, but the
> message is not actually written to the other end.
> 
> I know this problem is strictly related to ikvm, not netty. But I'd like to
> ask if there is anything that could be done to make sure the message is
> written to the socket. Is there any write queue that I could configure? Any
> know bug related to this scenario?
> 
> Cheers!
> 
> --
> Leandro Rodrigo Saad Cruz
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100406/9b50ff84/attachment-0001.bin