[
https://issues.apache.org/jira/browse/CASSANDRA-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875446#action_12875446
]
Jonathan Ellis commented on CASSANDRA-1057:
-------------------------------------------
I confess: I couldn't figure out how to get a patch from that link, to apply to
apache svn.
> Login information stored in threads may be reused.
> --------------------------------------------------
>
> Key: CASSANDRA-1057
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1057
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6
> Reporter: Kenny
> Priority: Minor
> Fix For: 0.6.3
>
>
> CassandraServer stores the login information in a ThreadLocal<AccessLevel>.
> CassandraDaemon starts the server with 64 threads. When the first 64 clients
> connect they should get their own thread, but after that threads will be
> reused.
> In a quick test I created a Server with 5 threads, and a
> ThreadLocal<Integer>, and the value is seen by new clients connecting.
> Thrift doesn't destroy the threads when a client disconnects. Maybe an option
> in Thrift would make more sense to make this method usable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
