It would be a lot easier to correlate messages that log4jdbc writes with
information available from the database itself if log4jdbc included in its
messages the process identifier used by the database.
One application of this feature would be to diagnose deadlocks. SQL Server will
report the process identifiers of the processes involved in a deadlock, and
log4jdbc reports statements executed, but there currently is no way to
correlate the two.
Original issue reported on code.google.com by t...@boemker.com on 12 Dec 2013 at 4:31
Original issue reported on code.google.com by
t...@boemker.com
on 12 Dec 2013 at 4:31