rocessor-thread holding on for a connection forever.
You could also try the logAbandonedConnection-Feature of DBCP ...
hth,
Marcus
> -Original Message-
> From: Henry Tong [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 26, 2007 8:36 AM
> To: Tapestry users
> Subject: Re:
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 ha
There's no good way to know when the user closes or navigates away
from the web page. (There is an "on close" event available in
Javascript. You might be tempted to send a signal to the server when
this happens, but the event isn't implemented the same way across all
browsers and if the user "clos
Hi,
any idea how to release connection when user close the web page?
Yours Sincerely,
Henry Tong
On 1/26/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...
On 1/25/07, Henry Ton
Allow only one connection in your connection pool and hit the app
until you find what section freezes / stops working...
On 1/25/07, Henry Tong <[EMAIL PROTECTED]> wrote:
Hi,
Our team are developing website using tapestry 4.1, honeycomb 0.3.3, hibernate
3.2.0.cr4, hivemind, DBCP 1.2.1 on Tomcat
