[
https://issues.apache.org/jira/browse/CASSANDRA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069145#comment-13069145
]
Jonathan Ellis commented on CASSANDRA-1405:
-------------------------------------------
bq. It is logged by thrift internally so we dont have much control over that
Let's submit a Thrift patch to fix that then. It's easy to get a Java-only
patch reviewed.
In the meantime I'm ok w/ turning org.apache.thrift log4j levels down to debug.
> Switch to THsHaServer, redux
> ----------------------------
>
> Key: CASSANDRA-1405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1405
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.8.3
>
> Attachments: 0001-log4j-config-change.patch,
> 1405-Thrift-Patch-SVN.patch, libthrift-r1026391.jar, trunk-1405.patch
>
>
> Brian's patch to CASSANDRA-876 suggested using a custom TProcessorFactory
> subclass, overriding getProcessor to reset to a default state when a new
> client connects. It looks like this would allow dropping
> CustomTThreadPoolServer as well as allowing non-thread based servers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
