ChannelUpstreamHandler.handleUpstream bug - InterestOps changed

[Kr0e]

Hi, thanks for your reply.
Unfortunately this issue still seems to be active. I looked into the code
and it did not look like a bug but more like intended. Here and there are a
few comments about this issue:

    void setInterestOps(
            NioSocketChannel channel, ChannelFuture future, int interestOps)
{
        boolean changed = false;
        try {
            // interestOps can change at any time and at any thread.!!!!!!!!
            // Acquire a lock to avoid possible race condition.

Setting the interestOps does not seem to be executed inside the I/O thread
which leads to the concurrent invocation.

Regards,

Chris

--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/ChannelUpstreamHandler-handleUpstream-bug-InterestOps-changed-tp6796758p6797206.html
Sent from the Netty User Group mailing list archive at Nabble.com.