Traces from custom module stop printing after redeploy
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
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>
Did this article resolve your issue ?