Postponing of ChunkedWriteHandlers hasNextChunk retrieval after write operation

[Tuomas Kiviaho]

Thanks for replying,


Trustin Lee wrote:
> 
> Are you mentioning the 182nd line of ChunkedWriteHandler that calls
> ChunkedInput.hasNextChunk()?  It would be nice if you could include
> the full thread dump.
> 
Sorry but I am about to change the approach completely.

Trustin Lee wrote:
> 
> Yes, the next chunk check could be postponed after Channels.write(...)
> call at line 214.  However, before making the modification, I'd like
> to know why dead lock occurs.
> 
The problem occured due to PushbackInputStream usage that I wasn't aware of.
My piping expected repeating request/response cycles and since chunk wasn't
send prior requesting a new chunk my implementation just stalled.

There no need to change the behaviour of ChunkedWriteHandler for my sake
anymore since I am not going to be using it for long.

--
Tuomas

-- 
View this message in context: http://n2.nabble.com/Postponing-of-ChunkedWriteHandlers-hasNextChunk-retrieval-after-write-operation-tp4024971p4069810.html
Sent from the Netty User Group mailing list archive at Nabble.com.