cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2061) Missing logging for some exceptions
Date Mon, 31 Jan 2011 05:04:11 GMT

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

Stu Hood commented on CASSANDRA-2061:
-------------------------------------

Based on anecdotal evidence (it exposed an exception I was expecting), this looks good. But
it looks like we can probably merge Debuggable(Scheduled)ThreadPool... they are appear to
be essentially identical now.

> Missing logging for some exceptions
> -----------------------------------
>
>                 Key: CASSANDRA-2061
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2061
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.2
>
>         Attachments: 2061-0.7.txt, 2061.txt
>
>
> {quote}Since you are using ScheduledThreadPoolExecutor.schedule(), the exception was
swallowed by the FutureTask.
> You will have to perform a get() method on the ScheduledFuture, and you will get ExecutionException
if there was any exception occured in run().{quote}

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

        

Mime
View raw message