[
https://issues.apache.org/jira/browse/CASSANDRA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Rolf updated CASSANDRA-6788:
--------------------------------------
Attachment: 6788-v3.txt
True, given that the ThreadPoolExecutor.afterExecute is a noop, the exception
should be rare.
Here's an alternative solution...in the hope that you prefer overrides to
factories and extra exception handling as much as I do :-)
> Race condition silently kills thrift server
> -------------------------------------------
>
> Key: CASSANDRA-6788
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6788
> Project: Cassandra
> Issue Type: Bug
> Reporter: Christian Rolf
> Assignee: Christian Rolf
> Attachments: 6788-v2.txt, 6788-v3.txt, race_patch.diff
>
>
> There's a race condition in CustomTThreadPoolServer that can cause the thrift
> server to silently stop listening for connections.
> It happens when the executor service throws a RejectedExecutionException,
> which is not caught.
>
> Silent in the sense that OpsCenter doesn't notice any problem since JMX is
> still running fine.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
