我尝试了SLF4J FAQ中的简单示例:
package com.aed.tests.logging;
import org.slf4j.LoggerFactory;
public class TestLogging
{
public TestLogging()
{
// TODO Auto-generated constructor stub
}
/**
* @param args
*/
public static void main(String[] args)
{
String s = "Hello world";
try
{
Integer i = Integer.valueOf(s);
}
catch(NumberFormatException e)
{
LoggerFactory.getLogger("simplelogger").error("Failed to format {}", s, e);
LoggerFactory.getLogger("simplelogger").error("Without parametrized string", e);
}
}
}
这是输出:
15:33:51,248000000 [SEVERE]simplelogger: Failed to format Hello world
15:33:51,275000000 [SEVERE]simplelogger: Without parametrized string
我使用java.util.logging作为日志记录实现,使用以下logging.properties
# Properties file which configures the operation of the JDK
# logging facility.
# The system will look for this config file, first using
# a System property specified at startup:
#
# >java -Djava.util.logging.config.file=myLoggingConfigFilePath
#
# If this property is not specified, then the config file is
# retrieved from its default location at:
#
# JDK_HOME/jre/lib/logging.properties
# Global logging properties.
# ------------------------------------------
# The set of handlers to be loaded upon startup.
# Comma-separated list of class names.
# (? LogManager docs say no comma here, but JDK example has comma.)
handlers=java.util.logging.ConsoleHandler
# Default global logging level.
# Loggers and Handlers may override this level
.level=ALL
# Loggers
# ------------------------------------------
# Loggers are usually attached to packages.
# Here, the level for each package is specified.
# The global level is used by default, so levels
# specified here simply act as an override.
# myapp.ui.level=ALL
# myapp.business.level=CONFIG
# myapp.data.level=SEVERE
# Handlers
# -----------------------------------------
# --- ConsoleHandler ---
# Override of global logging level
java.util.logging.ConsoleHandler.level=ALL
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
# HH:MM:ss,nanosec
java.util.logging.SimpleFormatter.format=%1$tT,%1$tN [%4$s]%3$s: %5$s %n
我希望看到异常的堆栈跟踪。我在配置中遗漏了什么吗?我可以用SLF4J或jdk日志记录以某种方式启用异常删除跟踪吗?
编辑在“标记为重复”之后。 我的问题不是“如何打印堆栈跟踪”,但是如何使用SLF4J的示例本身完成打印堆栈跟踪的工作,我仍然没有打印出堆栈跟踪。正如我所说,我使用log4j作为实现而不是java.util.logging打印出堆栈跟踪。所以这确实是java.util.logging配置错误的问题,当我发现时我给出了答案。
答案 0 :(得分:8)
这确实是为日志记录正确配置格式化程序的问题。
作为manual says,throwable是方法格式的第6个参数。所以我在logging.properties中添加了%6$s
格式:
java.util.logging.SimpleFormatter.format=%1$tT,%1$tN [%4$s]%3$s: %5$s %6$s %n
这是输出,显示堆栈跟踪:
17:29:33,314000000 [SEVERE]simplelogger: Failed to format Hello world
java.lang.NumberFormatException: For input string: "Hello world"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:492)
at java.lang.Integer.valueOf(Integer.java:582)
at com.aed.tests.logging.TestLogging.main(TestLogging.java:15)
17:29:33,344000000 [SEVERE]simplelogger: Without parametrized string
java.lang.NumberFormatException: For input string: "Hello world"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:492)
at java.lang.Integer.valueOf(Integer.java:582)
at com.aed.tests.logging.TestLogging.main(TestLogging.java:15)
答案 1 :(得分:0)
java.lang.Exception.toString()
不返回堆栈跟踪信息。来自documentation:
返回此throwable的简短描述
请参阅How can I convert a stack trace to a string?,然后记录您获得的String
。