Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Epic/Theme:

      Description

      It seems like Log4j has been promoted to a system module, so now it has the priority against portal jars, without declaring anything, by default.

      The workaround is to exclude the module from jboss deployment.

      This will be fixed in jboss 7.1.2: https://issues.jboss.org/browse/AS7-514

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  5 years, 26 weeks, 5 days ago