shell:source executes commands contained in a script • shell:stack-traces-print prints the full stack trace in the console when the execution of a command throws an exception • shell:tac captures the STDIN appender. You can change the log level to any Log4j valid values (from the most to less verbose): TRACE, DEBUG, INFO, WARN, ERROR, FATAL. The osgi:* appender is a special appender to send the log message • FINER • FINEST (lowest value) Additionally, de-facto standard log4j(2) levels can be used: • TRACE • DEBUG • INFO • WARN • ERROR • OFF • DEFAULT And because org.ops4j.pax.logging PID uses karaf

name="traceOutExchanges" value="true"/> trace="true" xmlns="http://camel.apache.org/schema/blueprint"> 0 码力 | 67 页 | 213.16 KB | 1 年前

3

framework (felix) STACK TRACES PRINTOUT The shell:stack-traces-print command prints the full stack trace when the execution of a command throws an exception. You can enable or disable this behaviour by the Karaf based distribution. For example simply add the following to your Option[] array to get TRACE logging: import static org.openengsb.labs.paxexam.karaf.options.KarafDistributionOption.logLevel; karafDistributionConfiguration("mvn:org.apache.karaf/apache-karaf/ 3.0.5/zip"), logLevel(LogLevel.TRACE) }; } DoNotModifyLogOption The option to modify the logging behavior requires that the container

s" value="true"/> trace="true" xmlns="http://camel.apache.org/schema/blueprint">

0 码力 | 64 页 | 812.01 KB | 1 年前

3