INFO log traces with STARTED/ STOPPED information are not displayed when deploying a module if using WildFly/JBoss version 22.0.0 or higher
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
- When a module is started or stopped, there is usually a log trace of level INFO showing that information. However, when using the application server WidlFly/JBoss with version 22.0.0 or higher, these traces are not displayed.
Resolution
- To show these traces again, it's necessary to add this line:
<module name="org.slf4j.impl"/>
in the file:
$LIFERAY_HOME/wildfly-23.0.2/standalone/deployments/ROOT.war/WEB-INF/jboss-deployment-structure.xml
inside the element exclusions.
The entire file will look like this:
?xml version="1.0"?>
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
<deployment>
<exclusions>
<module name="org.apache.log4j" />
<module name="org.hibernate" />
<module name="org.slf4j" />
<module name="org.slf4j.impl"/>
</exclusions>
<dependencies>
<module meta-inf="export" name="com.liferay.portal">
<imports>
<include path="META-INF" />
</imports>
</module>
<module name="javax.mail.api" />
<module name="org.apache.xerces" />
<module name="org.jboss.modules" />
</dependencies>
</deployment>
</jboss-deployment-structure>
- It's necessary to restart the server for the changes to take effect.
Did this article resolve your issue ?