HashedWheelTimer newTimout Exception (bug?)

Trustin Lee trustin at gleamynode.net
Wed Feb 11 17:20:59 EST 2009


Yep, I noticed that and my checkin includes your suggestion. :)

— Trustin Lee, http://gleamynode.net/



On Wed, Feb 11, 2009 at 9:29 PM, Dave Siracusa
<dave.siracusa at yellowbook.com> wrote:
>
> I added it around the stop as well.
> --Dave
>
> ________________________________
> From: Trustin Lee-3 (via Nabble) [mailto:ml-user+162222-252043752 at n2.nabble.com]
> Sent: Wednesday, February 11, 2009 12:09 AM
> To: Siracusa, Dave (YBUSA-KOP)
> Subject: Re: HashedWheelTimer newTimout Exception (bug?)
>
> Thanks for reporting this issue.  I've just checked in the fix.  It
> should work fine.  As of now, it has not been synchronized to the
> anonymous SVN repository.  It should appear soon - please wait for a
> while:
>
>  * http://fisheye.jboss.org/changelog/Netty/?cs=815
>
> - Trustin Lee, http://gleamynode.net/
>
>
>
> On Wed, Feb 11, 2009 at 1:55 AM, Dave Siracusa
> <dave.siracusa at ...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2306942&i=0>> wrote:
>
>>
>> I'm testing read/write timeout handling.
>> I rec'd the exception (below).
>> I believe we need synchronization around:
>>     if (!workerThread.isAlive()) {
>>            start();
>>        }
>>
>> --Dave
>> WARNING: HttpRequestHandler.Unexpected exception from downstream.
>> java.lang.IllegalThreadStateException
>>        at java.lang.Thread.start(Unknown Source)
>>        at
>> org.jboss.netty.handler.timeout.HashedWheelTimer.start(HashedWheelTimer.java:160)
>>        at
>> org.jboss.netty.handler.timeout.HashedWheelTimer.newTimeout(HashedWheelTimer.java:202)
>>        at
>> org.jboss.netty.handler.timeout.ReadTimeoutHandler.initialize(ReadTimeoutHandler.java:113)
>>        at
>> org.jboss.netty.handler.timeout.ReadTimeoutHandler.channelOpen(ReadTimeoutHandler.java:92)
>>        at
>> org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:103)
>>        at
>> org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:191)
>>        at
>> org.jboss.netty.channel.socket.nio.NioWorker$RegisterTask.run(NioWorker.java:661)
>>        at
>> org.jboss.netty.channel.socket.nio.NioWorker.processRegisterTaskQueue(NioWorker.java:227)
>>        at
>> org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:166)
>>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>> Source)
>>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> Source)
>>        at java.lang.Thread.run(Unknown Source)
>> --
>> View this message in context: http://n2.nabble.com/HashedWheelTimer-newTimout-Exception-%28bug-%29-tp2303551p2303551.html
>> Sent from the Netty User Group mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> netty-users mailing list
>> netty-users at ...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2306942&i=1>
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>
>
> _______________________________________________
> netty-users mailing list
> netty-users at ...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2306942&i=2>
> https://lists.jboss.org/mailman/listinfo/netty-users
>
> ________________________________
> This email is a reply to your post @ http://n2.nabble.com/HashedWheelTimer-newTimout-Exception-%28bug-%29-tp2303551p2306942.html
> You can reply by email or by visting the link above.
>
>
> --
> View this message in context: http://n2.nabble.com/HashedWheelTimer-newTimout-Exception-%28bug-%29-tp2303551p2308329.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>




More information about the netty-users mailing list