You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (Updated) (JIRA)" <ji...@apache.org> on 2011/10/21 01:34:11 UTC

[jira] [Updated] (HBASE-4640) Catch ClosedChannelException and document it

     [ https://issues.apache.org/jira/browse/HBASE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-4640:
--------------------------------------

    Attachment: HBASE-4640.patch

Patch that does what I described. The new message for ClosedChannelException is a bit different from the one I added in the book, but it still fits and currently users will likely hit the old version of the message.

I targeted this for 0.94 but I'm confident that it's harmless for 0.92
                
> Catch ClosedChannelException and document it
> --------------------------------------------
>
>                 Key: HBASE-4640
>                 URL: https://issues.apache.org/jira/browse/HBASE-4640
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4640.patch
>
>
> ClosedChannelException is a pretty obscure exception for the non-expert and doesn't tell you why you get it. We should instead catch it, print a WARN, don't print a stack trace, and add a line in the book about this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira