Request not executed when Channel Closed

[kireet]

Using 1.7.5/netty provider

Very occasionally the handler for one of my requests doesn't seem to be invoked (or there is some kind of bug in my handler). This only happens once every few days. I increased logging in my code and turned on debug logging in the async client code and found the problematic request. I see a line like:

NettyAsyncHttpProvider[DEBUG|New I/O worker #2|14:07:31]: Channel Closed: [id: 0x2f23978e,...

and then later down in the file I see:

NettyAsyncHttpProvider[DEBUG|feed-html-proc:1|14:07:31]:
Using cached Channel [id: 0x2f23978e, ...

Then I never see any logging for this request or channel again. Normally I see a verbose Request/Response log statement when the request completes.

I took a quick look at the code and there is some logic in writeRequest() where it checks if the channel is closed, if so it just returns. Is there perhaps some race condition here to do with closing a channel and using a cached channel?

[slandelle]

@kireet Sorry for taking so long.
See discussion in #415