Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      JBoss and perhaps other "containers"

      Description

      JBoss currently uses log4j for its own logging purposes. This causes numerous problems for applications that also want to use log4j for logging. JBoss has some documented methods for addressing the problems but none of them are particularly attractive. The goals for this issue should be:
      1. Allow each "application" to have its own configuration separate from JBoss' jboss-log4j.xml
      2. Allow applications to provide their own log4j components (Appenders, layouts, filters, etc) without having to put them in JBoss' classpath or the server/lib directory.

        Issue Links

          Activity

          Hide
          Ralph Goers added a comment -

          I have tested with JBoss 5 with a web app using SLF4J mapped to Log4j 2 using the Log4jContextListener. This works, however SLF4J is complaining that there are multiple SLF4J bindings. So far I have not been successful in eliminating this. Luckily it is choosing the binding within the web app so the application is behaving properly.

          Show
          Ralph Goers added a comment - I have tested with JBoss 5 with a web app using SLF4J mapped to Log4j 2 using the Log4jContextListener. This works, however SLF4J is complaining that there are multiple SLF4J bindings. So far I have not been successful in eliminating this. Luckily it is choosing the binding within the web app so the application is behaving properly.
          Hide
          Paul Benedict added a comment -
          Show
          Paul Benedict added a comment - Any relation to this technique that requires a custom webapp key? http://static.springsource.org/spring/docs/2.0.x/api/org/springframework/web/util/Log4jWebConfigurer.html
          Hide
          Ralph Goers added a comment -

          No. Spring's Log4jWebConfigurer is for Log4j 1.x. You would use Log4j 2's Log4jContextListener in place of that.

          Show
          Ralph Goers added a comment - No. Spring's Log4jWebConfigurer is for Log4j 1.x. You would use Log4j 2's Log4jContextListener in place of that.
          Hide
          Matt Sicker added a comment -

          So, uh, is this still a valid issue now that JBoss/WildFly uses JBoss-Logging which reminds me of commons-logging as it is?

          Show
          Matt Sicker added a comment - So, uh, is this still a valid issue now that JBoss/WildFly uses JBoss-Logging which reminds me of commons-logging as it is?

            People

            • Assignee:
              Unassigned
              Reporter:
              Ralph Goers
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development