[JBoss JIRA] Closed: (NETTY-52) IllegalArgumentException when trying to change the current interestOps

[Trustin Lee (JIRA)]

     [ https://jira.jboss.org/jira/browse/NETTY-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee closed NETTY-52.
----------------------------

    Fix Version/s: 3.0.0.CR5
       Resolution: Done


Should be fixed now..

> IllegalArgumentException when trying to change the current interestOps
> ----------------------------------------------------------------------
>
>                 Key: NETTY-52
>                 URL: https://jira.jboss.org/jira/browse/NETTY-52
>             Project: Netty
>          Issue Type: Bug
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>             Fix For: 3.0.0.CR5
>
>
> Exception in thread "pool-3-thread-6" java.lang.IllegalArgumentException: OP_WRITE can't be modified by user.
> 	at org.jboss.netty.channel.Channels.validateDownstreamInterestOps(Channels.java:738)
> 	at org.jboss.netty.channel.Channels.setInterestOps(Channels.java:631)
> 	at org.jboss.netty.channel.AbstractChannel.setInterestOps(AbstractChannel.java:170)
> 	at org.jboss.netty.channel.AbstractChannel.setReadable(AbstractChannel.java:192)
> 	at org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor.decreaseCounter(MemoryAwareThreadPoolExecutor.java:347)
> 	at org.jboss.netty.handler.execution.MemoryAwareThreadPoolExecutor.beforeExecute(MemoryAwareThreadPoolExecutor.java:279)
> 	at org.jboss.netty.handler.execution.OrderedMemoryAwareThreadPoolExecutor$ChildExecutor.run(OrderedMemoryAwareThreadPoolExecutor.java:208)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:619)
> Probably OP_WRITE flag has been changed at some point by NioWorker.  We actually doesn't even touch the OP_WRITE flag.  Let's just always clear the flag in the request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira