[CASSANDRA-13961] Safe castings to logback classes

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Labels: patch
• Assignee: Unassigned
• Reporter: Federico Fernández
• Created: 17/Oct/17 09:30
• Updated: 16/Apr/19 09:29
• Resolved: 17/Oct/17 12:36

Description

While working in an SBT plugin for I faced the problem: the system was injecting in the classpath the log4j implementation for SLF4J. This caused a ClassCastException in the startup process.

Cassandra uses logback but IMHO we shouldn't fail at runtime if SLF4J loads another implementation. Ideally, we should allow the users to choose their favourite implementation.

I've attached a patch that adds a instanceof checkings before casting the logback classes.

Thanks.

Issue Links

• duplicates: CASSANDRA-13396 Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager