This just tells you the code that ran *after* the offending code. Which if there are background process being fired by quartz for example, tells you nothing.
I would suggest whipping together a proxy around the connection manager and saving a exception (for it's stack trace) each time the code hands out a connection and then discards it everytime the connection is returned to the connection pool. Done properly and with jmx it becomes another tool that you can hand to your QA engineers so they can give you better bug reports. -Pat On 1/25/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Allow only one connection in your connection pool and hit the app until you find what section freezes / stops working...
