cassandra-commits mailing list archives

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

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

Jonathan Ellis commented on CASSANDRA-2061:
-------------------------------------------

STPE also notes,

bq. While this class inherits from ThreadPoolExecutor, a few of the inherited tuning methods
are not useful for it. In particular, because it acts as a fixed-sized pool using corePoolSize
threads and an unbounded queue, adjustments to maximumPoolSize have no useful effect.

We've wanted bounded queues in the past, and we definitely still use growable pools in places,
so that's another reason to keep both.

> 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