OSGI LogService only usable for levels WARNING and above

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 7.1.10 DXP FP3
• Fix Version/s: None
• Component/s: Core Infrastructure > Log Bridge
• Labels:
  • QA-TBD
  • ee-ts
• Fix Priority: 2

The logging method used all over the place (OSGI LogService + module-log4j.xml with osgi.logging.BUNDLE-Symbolic-Name) doesn't work anymore in 7.1 (FP3). You can still log through the OSGI LogService, but only at level WARNING and above. The log4j.xml still add an entry to the control panel, but it doesn't actually effect anything. I've tried both with stuff directly from the blade example repository and my own stuff (that both previously worked. Only way to get it to work now seems to be to replace the OSGI LogService with slf4j.

Prompted by Ray to test the following to confirm if the issue was configuration level of the defaul level in the new Log Service LoggerAdmin:

add a configuration file:
`org.osgi.service.log.admin.cfg` with the contents:
```ROOT="DEBUG"```

But this had noe effect.

Just a quick edit here: Seems that the exact same issue applies when using sl4j. So the only way to log with levels below WARN is to use liferays LogFactoryUtil which according to the documentation is depreciated.