Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Epic/Theme:
    • Similar Issues:
      Show 5 results 

      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

        Issue Links

          Activity

          Hide
          Igor Spasic added a comment -

          However, logs will look a bit odd:

          09:13:32,083 INFO  [stdout] (liferay/scheduler_dispatch-2) 09:13:32,083 DEBUG [BaseAsyncDestination:134] No message listeners for destination liferay/audit
          
          Show
          Igor Spasic added a comment - However, logs will look a bit odd: 09:13:32,083 INFO [stdout] (liferay/scheduler_dispatch-2) 09:13:32,083 DEBUG [BaseAsyncDestination:134] No message listeners for destination liferay/audit
          Hide
          Michael Saechang added a comment -

          Committed on:
          Portal 6.1.x CE GIT ID: 1a7fd537c3ca16723196dba113c6ff51cb92c9a9.
          Portal 6.2.x GIT ID: 9fee66a039b348d1ebe39efb0e3e3e0c3d1f584e.

          Show
          Michael Saechang added a comment - Committed on: Portal 6.1.x CE GIT ID: 1a7fd537c3ca16723196dba113c6ff51cb92c9a9. Portal 6.2.x GIT ID: 9fee66a039b348d1ebe39efb0e3e3e0c3d1f584e.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 40 weeks, 6 days ago

                Development

                  Structure Helper Panel