[
https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952024#comment-15952024
]
Jeff Jirsa commented on CASSANDRA-13396:
----------------------------------------
Changes back to bug, because even if the belief is that other loggers shouldn't
be encouraged, we surely can do better than throwing a cast exception
Given that log4j2 is likely faster than logback and has been suggested as far
back as 2013 CASSANDRA-5883 it seems like artificially forcing logback is a
position that would need to be more rigorously defended - I'm +1 on this change
conceptually (but this is not a review).
> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> ----------------------------------------------------------------
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
> Issue Type: Bug
> Reporter: Edward Capriolo
> Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
