John, I don't want you to think I am ignoring this. I've been at a conference this week and have been a little bit tight for time. I plan on looking at this and LOG4J2-50 in the next couple of days. Hopefully your patch will fix it.
Ralph On Sep 18, 2011, at 6:28 PM, John Vasileff (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/LOG4J2-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > John Vasileff updated LOG4J2-51: > -------------------------------- > > Attachment: (was: > 0002-fix-for-Category.getInstance-returning-cached-Logger.patch) > >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
