Github user ok2c commented on the issue:
    @cakofony Always returning Integer.MAX_VALUE from 
`AsyncDataProducer#available` does not sound right me. Simple producers do that 
if they are self-contained and can always produce more data if the underlying 
channel is ready. This is not the case with complex producers such as 
`AsyncDataProducer` that may not always have data to write to the channel. By 
returning Integer.MAX_VALUE from `AsyncDataProducer#available` one can cause 
the I/O reactor spin busily and produce no data. 
    We need to think of a better fix. How reliably can you reproduce the issue 
and would it be possible to make a junit? 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to