奇怪的错误：CLOSE BY CLIENT STACK TRACE [英] Weird Error: CLOSE BY CLIENT STACK TRACE

问题描述

大家好我有一个使用Hibernate来检索数据库中的数据的Web应用程序。而在服务器端，有些疑问会定期出现。

  16：04：22,227 DEBUG NewPooledConnection：491  -  com.mchange.v2.c3p0.impl。 NewPooledConnection @ ef46613由客户端关闭。 
 java.lang.Exception：DEBUG  -  CLOSE BY CLIENT STACK TRACE 
 at com.mchange.v2.c3p0.impl.NewPooledConnection.close（NewPooledConnection.java:491）
 at com。 mchange.v2.c3p0.impl.NewPooledConnection.close（NewPooledConnection.java:191）
 at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool $ 1PooledConnectionResourcePoolManager.destroyResource（C3P0PooledConnectionPool.java:470）
 at com.mchange.v2.resourcepool.BasicResourcePool $ 1DestroyResourceTask.run（BasicResourcePool.java:964）
 at com.mchange.v2.async.ThreadPoolAsynchronousRunner $ PoolThread.run（ThreadPoolAsynchronousRunner.java:547）
 16 ：09：42,310 DEBUG C3P0PooledConnectionPool：476  - 成功销毁PooledConnection：com.mchange.v2.c3p0.impl.NewPooledConnection@32ef0763 
 16：09：42,310 DEBUG BasicResourcePool：967  - 成功销毁资源：com.mchange.v2。 c3p0.impl.NewPooledConnection@32ef0763 
 16：09：42,310 DEBUG GooGooStatementCache：319  -  EN TER方法：closeAll（org.postgresql.jdbc4.Jdbc4Connection@42df0af8）！ -  num_connections：1 
  

任何人都可以帮我解决这个问题吗？非常感谢！

解决方案

这是在C3P0中触发此日志语句的代码：

  if（logger.isLoggable（MLevel.FINEST））
 logger.log（MLevel.FINEST，this +由客户端关闭，
 new Exception（DEBUG  -  CLOSE BY CLIENT STACK TRACE））; 
  

请注意：

1. 这不是一个例外，新的Exception 仅用于显示调试目的的执行路径。




2. 是的，这只是一个调试消息（实际上， FINEST 是 java.util中可能的最低级别。日志记录）。

为了解决这个问题：忽略并调整日志级别以跳过这些。

Hi all I have a web application which use Hibernate to retrieve data in the database. And in the server side some execeptions come out at regular interval. Below is the exception logs.

    16:04:22,227 DEBUG NewPooledConnection:491 - com.mchange.v2.c3p0.impl.NewPooledConnection@ef46613 closed by a client.
    java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
        at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:491)
        at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:191)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470)
        at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964)
        at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
    16:09:42,310 DEBUG C3P0PooledConnectionPool:476 - Successfully destroyed PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@32ef0763
    16:09:42,310 DEBUG BasicResourcePool:967 - Successfully destroyed resource: com.mchange.v2.c3p0.impl.NewPooledConnection@32ef0763
    16:09:42,310 DEBUG GooGooStatementCache:319 - ENTER METHOD: closeAll( org.postgresql.jdbc4.Jdbc4Connection@42df0af8 )! -- num_connections: 1

Could anyone helps me with this problem? Thanks a lot!

解决方案

This is the code that triggers this log statement in C3P0:

if ( logger.isLoggable( MLevel.FINEST ) )
  logger.log( MLevel.FINEST, this + " closed by a client.", 
            new Exception("DEBUG -- CLOSE BY CLIENT STACK TRACE") );

Note that:

1. This is not an exception, the new Exception is used merely to show execution path for debug purposes.

2. And yes, this is only a debug message (actually, FINEST is the lowest possible level in java.util.logging).

To wrap this up: ignore and tune your logging levels to skip these.

这篇关于奇怪的错误：CLOSE BY CLIENT STACK TRACE的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！