[jboss-jira] [JBoss JIRA] (LOGMGR-70) [log4j-jboss-logmanager] When adding non-log4j loggers the parent handlers are not invoked

Tue Aug 13 09:03:26 EDT 2013

    [ https://issues.jboss.org/browse/LOGMGR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796512#comment-12796512 ] 

Martin Cekal commented on LOGMGR-70:
------------------------------------

Hello, is there any patch for EAP6.1 to have this issue fixed? Thanks

> [log4j-jboss-logmanager] When adding non-log4j loggers the parent handlers are not invoked
> ------------------------------------------------------------------------------------------
>
>                 Key: LOGMGR-70
>                 URL: https://issues.jboss.org/browse/LOGMGR-70
>             Project: JBoss Log Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> In the {{JBossAppenderHandler.doPublish()}} the logger name is checked from the record. In the case where a parent loggers handlers are used, the logger names don't match therefore the record is not published.
> The ideal solution is to remove the logger name match which could be a relic from a previous version. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira