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

[James Perkins (JIRA)]

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

James Perkins commented on LOGMGR-70:
-------------------------------------

Doesn't look like it. This is the commit that fixes it, https://github.com/jboss-logging/log4j-jboss-logmanager/commit/fbd434606173376c9be80d051cbf586c0a1e031b. It's in the [master|https://github.com/jboss-logging/log4j-jboss-logmanager/commits/master] upstream but on the [1.0|https://github.com/jboss-logging/log4j-jboss-logmanager/commits/1.0] branch which 1.0.2.Final is based on and it's the latest release. 

I don't have the permissions to cut a release otherwise I would :)
                
> [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