Picking log4j2 for mule
Download as PPTX, PDF0 likes1,158 views
This document discusses how Mule applications use Log4j2 for logging by default. It describes the log4j2 configuration file locations that Mule will search and how to configure a Mule application to use a log4j2 file from a custom location. The document provides an example of creating a common log4j2 configuration file in an external location, specifying that location in the application context, and verifying that the application logs using the external file.
Picking log4j2 for mule
- 1. By Anirban Sen Chowdhary
- 2. For logging, Mule ESB uses slf4j, which is a logging facade that discovers and uses a logging strategy from the classpath, such as log4j2 or the JDK Logger. By default, Mule includes log4j2, which is configured with a file called log4j2.xml. We all know how to configure and tweak our log4j2 in our application. In these slides we will demonstrate of picking a log4j2 file from a specific location of our choice.
- 3. By default, logging in Mule is done asynchronously and at a level greater than or equal to INFO, and thus discards log messages at the DEBUG or TRACE level. In Anypoint Studio, log4j2.xml appears in the src/main/resources path. When an application is deployed, Mule looks for a log4j2 file in the location, as listed below:- • log4j2-test.xml in the application classpath • log4j2.xml in the application classpath • log4j2-test.xml in the domain classpath • log4j2.xml in the domain classpath • log4j2-test.xml in MULE_HOME/conf • log4j2.xml in MULE_HOME/conf
- 4. We can force our Mule application to pick the log4j2 file from the location we want. Yes, in our application, the log4j2 file will be loaded from the path we will be specifying
- 6. Let us construct our log4j2.xml and rename it as common-log4j2.xml so that we can highlight our own log4j2.xml and place it in an external location outside our Mule application. A glimpse of our is as common-log4j2.xml follows :-
- 7. Next, we will create a Mule file that will contains the Spring Application Context that will pick our log4j2.xml which we named as common-log4j2.xml from the external path mentioned:-
- 8. Here you can see the path our log4j2.xml is specified as a property and the value will be picked from mule-app.properties file. We will mention the path of our log4j2.xml which we called as common- log4j2.xml in mule-app.properties file as follows:- And now we need to place ourcommon-log4j2.xml in the path mentioned in the properties file from where Spring Application Context will pick up the file for logging our application. Please note: In Standalone server, you need to pass dynamically these System properties value as VM argument as :- -M-Dlog4j2.path=file:///E:/common- log4j2.xml
- 10. Now, when we start our Mule application, we will see in our console that ourlog4j2.xml file called as common-log4j2.xml is selected from the external path we mentioned in our Application Context for logging of our application:-
- 11. And if you look into our common-log4j2.xml file, you will find that we have configured <RollingFile/> appenders, which means our application will create a log file :- If we open this file, we will find our application specific log.
- 12. So, here you can see how to use a select our own log4j2.xml file from any external location dynamically. !!!….You can now try this example by your own and force your Mule application to pick file of your choice from your selected path