Logging OSGi internals https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=118582907 2026-04-04T04:27:16Z 2026-04-04T04:27:16Z David H Nebinger https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=118586776 2020-02-25T15:11:40Z 2020-02-25T15:11:40Z

There is a lot happening, sure, but none of it is logging.<br /><br />Wrapping code with if (_log.isDebugEnabled()) seems like a great way to control whether a log message is generated, but even this adds overhead. In single instances, the overhead is negligible, but if you have a server doing this check frequently while trying to serve thousands of concurrent requests, the overhead is measurable and significant.<br /><br />For that reason, there is little if any logging decorating the Liferay code, typically you&#39;ll only find it at key points where errors can originate outside of Liferay&#39;s control and due to customization or configuration.<br /><br />So the TL;DR version, the best way to understand what is going on under the hood is by a deep code dive or live debugging.

David H Nebinger 2020-02-25T15:11:40Z Jan Tošovský https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=118582906 2020-02-25T10:40:59Z 2020-02-25T10:40:59Z

In LR Server Administration there are 11 OSGi related categories in the Log Levels tab. Even all are set to the ALL level, when redeploying the module I can only see two lines STOPPED xxx and STARTED xxx in the server log.<br /><ul style="list-style: disc outside;"><li>aQute.bnd.osgi     </li><li>com.liferay.osgi.felix.file.install.configuration.cleaner.internal     </li><li>com.liferay.osgi.log.service.extender.internal.OSGiLogServiceExtenderBundleActivator     </li><li>com.liferay.portal.osgi.debug.declarative.service.internal.UnsatisfiedComponentScanner     </li><li>com.liferay.portal.osgi.debug.internal.osgi.commands.SystemCheckOSGiCommands     </li><li>com.liferay.portal.osgi.debug.spring.extender.internal.UnavailableComponentScanner     </li><li>com.liferay.portal.osgi.web.wab.generator.internal.WabGenerator     </li><li>com.liferay.portal.osgi.web.wab.generator.internal.processor.WabProcessor     </li><li>osgi.logging     </li><li>osgi.logging.org_apache_felix_fileinstall     </li><li>osgi.logging.org_eclipse_osgi </li></ul>I believe there are lots of details what is happening under the hood.<br />Deploying one my module breaks functionality in other modules and I believe there could be some details why.

Jan Tošovský 2020-02-25T10:40:59Z