[
https://issues.apache.org/jira/browse/CASSANDRA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759146#action_12759146
]
Jun Rao commented on CASSANDRA-455:
-----------------------------------
"if get is causing the cancel even w/o any exceptions being involved then I
guess you'll need to source dive in ScheduledThreadPoolExecutor to see what is
going on."
That seems to be the case. Here is what happens.
Without exception:
When DebuggableThreadPoolExecutor.logFutureExceptions(r) is called in
afterExecute(), tasks are no longer executed afterwards. When
DebuggableThreadPoolExecutor.logFutureExceptions(r) is removed, tasks are
scheduled as expected.
With exception:
If DebuggableThreadPoolExecutor.logFutureExceptions(r) is removed, exception is
not logged.
> DebuggableScheduledThreadPoolExecutor only schedules a task once
> ----------------------------------------------------------------
>
> Key: CASSANDRA-455
> URL: https://issues.apache.org/jira/browse/CASSANDRA-455
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Jun Rao
>
> DebuggableScheduledThreadPoolExecutor only schedules a task exactly once,
> instead of periodically. This affects scheduled flushers and periodic hints
> delivery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
