JBoss AS 7.1.1 does not longer honoring Log4j level settings

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.1.20 EE GA2, 6.2.0 CE M2
• Fix Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2, --Sprint 11/12, 6.2.0 CE M2
• Component/s: Infrastructure, Infrastructure > App Servers
• Labels: None
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Epic/Theme:
  • Quick_Win
• Similar Issues: Show 5 results ; ;

  LPS-26864	Liferay 6.1 EE and JBOSS 7.1.1 - Log Levels Not Displaying
  LPS-2987	Setting log4j level should also set jdk logging level
  LPS-34359	CKEditor is broken on JBoss 7.1.1
  LPS-27173	Upgrade to JBoss 7.1.1
  LPS-2734	When a community's pages are bound to a virtual host, Login Portlet does not honor "company.security.auth.requires.https=true" setting

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

[Igor Spasic]

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

[Michael Saechang]

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