[jboss-jira] [JBoss JIRA] (WFCORE-1429) Add property to skip LogManager check at startup

James Perkins (JIRA) issues at jboss.org
Tue Aug 16 17:20:00 EDT 2016


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

James Perkins commented on WFCORE-1429:
---------------------------------------

One thing to note about wrapping the log manager. If JBoss Logging will use the JUL provider instead of the JBoss Log Manager provider. That means things like MDC and NDC will behave differently and likely not be usable when writing log messages.

> Add property to skip LogManager check at startup
> ------------------------------------------------
>
>                 Key: WFCORE-1429
>                 URL: https://issues.jboss.org/browse/WFCORE-1429
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Logging
>            Reporter: Dominique Broeglin
>            Assignee: James Perkins
>            Priority: Minor
>             Fix For: 3.0.0.Alpha6
>
>
> At startup, Wildfly checks that the default log manager (as returned by {{java.util.logging.LogManager.getLogManager()}} ) is {{org.jboss.logmanager.LogManager}}:
> https://github.com/wildfly/wildfly-core/blob/master/logging/src/main/java/org/jboss/as/logging/LoggingExtension.java#L146
> This breaks some cases where the LogManager is wrapped because of the needs of that particular JVM like in OSv ( https://github.com/cloudius-systems/osv/blob/master/java/runjava/src/main/java/io/osv/jul/LogManagerWrapper.java ).
> As suggested on the mailing list, I would like to propose adding a property to bypass that check. Something along the lines of "jboss.logging.logManagerCheck = false/true"



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list