> One thing you can do is to insert the P6Spy database driver into your app > -- this jdbc driver wrapper will provide logging at the jdbc level, which > would let you see what's going on without having to enable java logging.
To see what part of the application is issuing the request, you could take the sources (available from http://p6spy.svn.sourceforge.net/viewvc/p6spy/trunk/src/main/java ) and insert logging of stack traces. That should at least point you in the direction what's responsible. There's actually (commented-out) code for that in com/p6spy/engine/common/P6LogQuery.java. Maybe do that only if the statement is the one that shouldn't happen so you don't get huge logs. HTH Jo
