ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolas Kyriazopoulos Panagiotopoulos" <nikola...@gmail.com>
Subject Re: Ibatis throttle - possible deadlock (ibatis 2.2, 2.3)
Date Tue, 15 Jan 2008 12:48:13 GMT
>  You could set the java.sql logging category to DEBUG and then you'd be able
> to trace which statements are blocking.  This will generate a lot of logfile
> data, so be ready for it.

To identify such issues we expect to see statements executed without
having a corresponding result set? (I'm tempted to deactivate logging
result sets as following, as they practically double the size of logs)

log4j.logger.java.sql.Connection=debug
log4j.logger.java.sql.Statement=debug
#log4j.logger.java.sql.PreparedStatement=debug
#log4j.logger.java.sql.ResultSet=debug

Mime
View raw message