Exception on connect being caught by response handler

[jgalyan]

The operationComplete callback isn't being executed--the ConnectionRefused
exception is going directly to my response handler's exceptionCaught method,
which is why I'm puzzled.  If the connection was refused, then it seems like
I should find that out in operationComplete in the ChannelFutureListener,
which is how this worked before, in another project I used Netty for.

Did the contract change between 3.2.1 and 3.2.3?  Or am I mistaken in my
belief that this used to work... or is the exception maybe misleading?
-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Exception-on-connect-being-caught-by-response-handler-tp5764119p5766875.html
Sent from the Netty User Group mailing list archive at Nabble.com.