I am finally (at the TRACE level) seeing something odd. The NioProcessor-2 is spitting out a SENT: message (from the client handler) saying:
SENT: HeapBuffer[pos=0 lim=0 cap=0: empty] But I'm doing the flip(). I'm not adding any carriage returns. I'm not ever sending out a blank string. Would this be causing the connection to close? -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Monday, May 13, 2013 1:14 PM To: [email protected] Subject: Re: Help with NioSocketConnector Le 5/13/13 6:16 PM, Whitener, Winona T. a écrit : > More information: > > In my latest test run, the encoder/decoder did work successfully. They > parsed out my start of message and end of message characters correctly. They > are applied to both the acceptor and connector. The messages going to and > from the acceptor both are applied correctly. There is no idle timeout > applied to either end. No exceptions are caught at either end. I have seen > exceptions while attempting to initially set up the encoder/decoder and those > were caught--so I know that the exception handling on both ends is there and > catches exceptions. So assuming the codec is working, that no exception is thrown, there must be something wrong with the way you use the connector. Keep in mind that this is an asynchronous framework, ie any call you make (write, for instance) will not block. It's hard to know what's wrong n your code without seing it... -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
