You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/01/27 16:36:43 UTC
[jira] Updated: (CASSANDRA-2061) Missing logging for some
exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2061:
--------------------------------------
Attachment: 2061.txt
As near as I can tell, an exception thrown on a scheduled task will never kill the executor, just like in TPE. I don't remember why the author [me] wrote that code -- probably because it was replacing Timer and TimerTask, and an uncaught exception in a TimerTask _will_ kill the timer.
Patch removes RetryingSTPE and replaces with DebuggableSTPE that has an afterExecute copied from DTPE.
> 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
> Fix For: 0.7.2
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.