Traces from custom module stop printing after redeploy

Issue

  • A custom module prints traces the first time it's deployed but not if redeployed.
  • After restarting Liferay it works again.

Environment

  • Quarterly Release 2023.Q3, 2023.Q4, 2024.Q1
  • Liferay DXP 7.4

Resolution

  • This can happen if the configuration file module-log4j.xml uses an element <level> inside of <logger> instead of adding it as an attribute.
  • So, instead of
    <Loggers>
    <logger name="testlog4j2redeploy.portlet.TestLog4J2RedeployPortlet" additivity="false">
    <level value="info"/>
    <appender-ref ref="TestLog4J2RedeployPortletLogFile" />
    </logger>
    </Loggers>
    use
    <Loggers>
    <logger level="info" name="testlog4j2redeploy.portlet.TestLog4J2RedeployPortlet" additivity="false">
    <appender-ref ref="TestLog4J2RedeployPortletLogFile" />
    </logger>
    </Loggers>
この記事は役に立ちましたか?
0人中0人がこの記事が役に立ったと言っています