Hey list,
I'm trying to find information on how the error about closing all
dangling connections gets generated.
I'm using a library that works by attaching a connection to each
request and closes it automatically using a ServletRequestListener. As
far as I can tell, this behavior is causing
On Jul 26, 2007, at 7:47 AM, Paul Davis wrote:
Hey list,
I'm trying to find information on how the error about closing all
dangling connections gets generated.
At the end of the top-level request, Resin rolls back the
UserTransaction, and closes any connections that haven't been
closed.
Scenario: Primary server is down and the backup is active, Resin 3.0.23,
The session store is being reloaded 4- 5 times, per click by user.
I believe this is because I have some CSS that loads images. The store
is even refreshed
when the user just hovers over an image !
Is there a way to tell
Use a filter:
Open connection
try {
doFilter
} finally {
Close connection
}
_
Robert Leland INTEGRITYOne (Formerly PRIZUM)
P: (703) 581-6522 1900 Campus Commons Drive
F: (703) 476-7405Reston,
