ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koka Kiknadze" <226...@gmail.com>
Subject Logging problem
Date Tue, 20 Feb 2007 14:25:20 GMT
I'm debugging multithreaded application for connection leaks and found that
iBatis logging is not quite helpful. E.g. I have output like:

2007-02-20 17:15:17,406 DEBUG [com.ibatis.common.jdbc.SimpleDataSource] -
Created connection 30426707.
2007-02-20 17:15:17,406 DEBUG [java.sql.Connection] - {conn-100000}
Connection
2007-02-20 17:15:17,421 DEBUG [java.sql.Connection] - {conn-100000 30426707}
Preparing Statement:          select * from ....
2007-02-20 17:15:17,640 DEBUG [com.ibatis.common.jdbc.SimpleDataSource] -
Returned connection 30426707 to pool.

Note that log statements for creating (and also for checking out) and
returning connection from pool (i.e. statements for [
com.ibatis.common.jdbc.SimpleDataSource] )  are marked with hashCode
30426707, while statements for preparing statements - with {conn-100000}
where 100000 seems to be just autoincremental number. It would have been
quite helpful if the connection hashCode were included in [
java.sql.Connection] log statements also.

Am I missing something? Is there a way to track connection
lifecycle/activity in the log files?
TYA

Mime
View raw message