You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2011/09/26 09:06:26 UTC
[jira] [Commented] (LOG4J2-51) ClassCastException in Category
logger
[ https://issues.apache.org/jira/browse/LOG4J2-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114494#comment-13114494 ]
Ralph Goers commented on LOG4J2-51:
-----------------------------------
Unfortunately, this patch breaks the ClassLoaderContextSelector as it will now not be able to determine what ClassLoader the Logger should be associated with.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org