[
https://issues.apache.org/jira/browse/LOG4J2-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114516#comment-13114516
]
Ralph Goers commented on LOG4J2-51:
-----------------------------------
I applied the patches above and LogManager.getLogger() is still throwing a
ClassCastException. In addition a second unit test is failing but I believe you
said that error is fixed by the patch for LOG4J2-50.
> ClassCastException in Category logger
> -------------------------------------
>
> Key: LOG4J2-51
> URL: https://issues.apache.org/jira/browse/LOG4J2-51
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Reporter: John Vasileff
> Priority: Blocker
> Attachments:
> 0001-add-test-for-Category-when-using-a-log4j2-Logger.patch,
> 0002-fix-for-Category.getInstance-returning-cached-Logger.patch,
> 0003-remove-dangerous-logger-factory-override.patch
>
>
> When a Category is "created" with the same name as a previously created
> log4j2 Logger, a ClassCastException occurs when calling category.l7dlog(...)
> and others.
> See LOG4J2-50 for additional symptoms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
