NPE in HexDumpProxyInboundHandler example

[paulcager]

Running org.jboss.netty.example.proxy.hexDumpProxy I get an NPE in HexDumpProxyInboundHandler.channelInterestChanged when a new connection arrives:

    public void channelInterestChanged(ChannelHandlerContext ctx,
            ChannelStateEvent e) throws Exception {
        // If inboundChannel is not saturated anymore, continue accepting
        // the incoming traffic from the outboundChannel.
        synchronized (trafficLock) {
            if (e.getChannel().isWritable()) {
                outboundChannel.setReadable(true);
            }
        }
    }

I think this happens because in channelOpen inboundChannel.setReadable(false); is called before executing outboundChannel = f.getChannel();

[normanmaurer]

Could you please include the stacktrace ?

[paulcager]

Here's the stack trace. I'm using a recent 3.4.1.Final-SNAPSHOT for testing.

Proxying *:1919 to www.google.co.uk:80 ...
java.lang.NullPointerException
    at org.jboss.netty.example.proxy.HexDumpProxyInboundHandler.channelInterestChanged(HexDumpProxyInboundHandler.java:102)
    at org.jboss.netty.channel.Channels.fireChannelInterestChanged(Channels.java:361)
    at org.jboss.netty.channel.Channels$3.run(Channels.java:349)
    at org.jboss.netty.channel.socket.ChannelRunnableWrapper.run(ChannelRunnableWrapper.java:41)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processEventQueue(AbstractNioWorker.java:352)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:236)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)

[normanmaurer]

Fixed thanks!