$MULE_HOME/conf/log4j.properties 여기다가 만들면 된다.
This directory is used for tracing the execution of the Mule container.
Top-level logger for the Mule container is configured in "$MULE_HOME/conf/log4j.properties" or
"$MULE_HOME/conf/log4j.xml".
*** Xml format has higher priority and will be used if found or in presence of both xml and properties configs. ***
Log4j xml docs: http://wiki.apache.org/logging-log4j/Log4jXmlFormat
Container-level logging is written to the $MULE_HOME/logs/mule.log file.
Application-level logging supports 2 modes:
1. No log4j configuration packaged with the app (either in app's lib or classes) -
a rolling log file is automatically created by Mule:
$MULE_HOME/logs/mule-app-<appName>.log
The format is the same as the default Mule config.
2. A log4j configuration is packaged with the app - no default log file is created
by Mule and app has a full control (and responsibility) to configure logging.
*** TIP: use ${mule.home} placeholder in log4j.properties to resolve the Mule's directory (e.g. for file appenders). ***
In addition to the application's output, the wrapper also sends any JVM-level or
OS-level errors/warnings to the log file. This means that if the JVM crashes
and automatically restarts (enabled by default), the time and cause of the crash
will remain in the log file after the JVM restarts.
'Java > Mule ESB' 카테고리의 다른 글
| Mule log4j.properties 설정 위치 (1) | 2012/03/29 |
|---|---|
| Mule Interceptor Event Flow (0) | 2011/07/13 |
웹 서비스의 동적 발견과 호출.pdf