The advantage of having per-service log files is that it is very easy to analyze/monitor what went wrong in this particular Proxy Service by looking at the service log. Enabling this feature will not terminate the
wso2-esb.log file being keeping the logs about this service, the complete log will contain every log statement including the service logs that you have configured to be logged into a different log file. In other words, the service log is an additional log file, which will contain a copy of the logs to that particular service.
Follow the instructions below to configure the logs of a particular service (to be more specific a Proxy Service) to be logged into a given log file.
It has a Proxy Service named
log4j to log the service specific logs to a file called
stock-quote-proxy-service.log in the logs directory of the ESB installation directory.
2.1. Open up the
log4j.properties file found in the
/repository/conf directory of the WSO2 ESB installation directory using your favorite text editor and add the following section to the end of the file starting in a new line.
2.2. Save the file.
3. Try it out. By default, the configuration does not do any logging at run time, so configure the Proxy Service in-sequence to contain a log mediator to log the message at "Full" log level.
Execute the sample client after starting the ESB with sample 150:
and the sample axis2 server with the
SimpleStockQuote service deployed on it as per stated in the sample documentation.
4. Inspect the logs directory of the ESB installation directory to see the
Further to demonstrate the log file rotation this particular logger was configured to rotate the file in each minute when ever there is a log going into the service log, so if you execute the sample client once again after 1 minute you will be able to see the service log file rotation as well.
You can see the source here.