cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Passiouk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
Date Mon, 03 Apr 2017 09:25:42 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953179#comment-15953179
] 

Anton Passiouk commented on CASSANDRA-13396:
--------------------------------------------

All I was asking for is avoid crashing, and I am concious that I am not in a standard use-case.
I am perfectly fine with a big warning in the log saying that using something other than logback
is at my own risk + the the doc that states that nothing but logback is officially supported
which makes you not responsible for any bug. 

Of course, as Benjamin says, there is still the risk of you investigating an issue without
knowing that a different logger is used, but if you are really paranoid you can also imaging
people configuring their logback in a very inefficient or wrong way and create crappy issues
while being perfectly "legal".

> 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)

Mime
View raw message