Question

15:31:58,339 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.JdbcResourceRegistryImpl:211 - Closing prepared statement [com.mysql.jdbc.JDBC4PreparedStatement@7bf4109: select producttyp0_.id as id5_, producttyp0_.name as name5_ from production_queue.Product_Type producttyp0_ where producttyp0_.name='Phone Case']
15:31:58,339 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler:88 - Handling invocation of statement method [invalidate]
15:31:58,339 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:234 - Starting after statement execution processing [ON_CLOSE]
15:31:58,339 TRACE Grizzly(1) org.hibernate.engine.internal.StatefulPersistenceContext:1016 - Initializing non-lazy collections
15:31:58,339 TRACE Grizzly(1) org.hibernate.internal.SessionImpl:1383 - Setting cache mode to: NORMAL
15:31:58,339 TRACE Grizzly(1) org.hibernate.internal.SessionImpl:340 - Closing session
15:31:58,340 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:193 - Closing logical connection
15:31:58,340 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler:110 - Handling invocation of connection method [close]
15:31:58,340 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler:206 - Invalidating connection handle
15:31:58,340 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.JdbcResourceRegistryImpl:205 - Closing JDBC container [org.hibernate.engine.jdbc.internal.JdbcResourceRegistryImpl@4557b620]
15:31:58,340 DEBUG Grizzly(1) org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:314 - Releasing JDBC connection
15:31:58,341 DEBUG Grizzly(1) org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:332 - Released JDBC connection
15:31:58,341 DEBUG Grizzly(1) org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler:219 - HHH000163: Logical connection releasing its physical connection
15:31:58,341 TRACE Grizzly(1) org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:207 - Logical connection closed
WARNING: Exception during FilterChain execution
WARNING: service exception

尽管配置了log4j.rootCategory=TRACE, stdout，但它似乎无法帮助我获得有关此异常的更多详细信息。

log4j.properties

log4j.rootCategory=TRACE, stdout

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %t %c:%L - %m%n

Answer 1

记录器看起来配置正确，但这并不意味着有问题的代码正确调用它。如果简单地将记录器称为LOG.warn(e)，它将仅记录异常的消息，而不是完整的堆栈跟踪。

考虑到这一点，奇怪的是时间戳和类文件不存在于日志中。您确定Grizzly使用Log4J并且没有通过commons-logging或Java Util Logging进行自己的日志记录吗？

如何获取此异常的堆栈跟踪？

1 个答案: