incubator-awf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnathan Meehan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DEFT-149) IOLoop.start() may throw CancelledKeyException
Date Tue, 06 Sep 2011 14:32:10 GMT

    [ https://issues.apache.org/jira/browse/DEFT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098033#comment-13098033
] 

Johnathan Meehan commented on DEFT-149:
---------------------------------------

Would it not actually be better to handle the exception known, rather than blanket cover any
exception at all? I think the expected range of exceptions should be known, and the response
to each explicit.

> IOLoop.start() may throw CancelledKeyException
> ----------------------------------------------
>
>                 Key: DEFT-149
>                 URL: https://issues.apache.org/jira/browse/DEFT-149
>             Project: Deft
>          Issue Type: Bug
>             Fix For: 0.4.0
>
>
> Exception in thread "I/O-LOOP" java.nio.channels.CancelledKeyException
>         at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
>         at sun.nio.ch.SelectionKeyImpl.readyOps(SelectionKeyImpl.java:69)
>         at java.nio.channels.SelectionKey.isAcceptable(SelectionKey.java:342)
>         at org.deftserver.io.IOLoop.start(IOLoop.java:77)
> Would it be a reasonable solution to change the catch clause from catch(IOException e)
to catch(Exception e)?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message