Hi Phil,
ah great, I can confirm that it is logging something if I add the auto
flush:
https://gist.github.com/ecki/345ee08ac97820972fe7#file-result-autoflush4s-txt
(It even logs the active statements, so I guess it tries to kill them (but
get blocked by my initial problem). What do you think
Forgot to copy list
Forwarded Message
Subject:Re: [dbcp] Abandon Connection - not Logging in standalone
Date: Sun, 26 Jul 2015 17:02:38 -0700
From: Phil Steitz phil.ste...@gmail.com
To: Bernd Eckenfels e...@zusammenkunft.net
On 7/25/15 8:19 AM, Bernd
On 7/23/15 4:18 PM, Bernd Eckenfels wrote:
Hello,
I noticed that with Oracle drivers you cannot kill a busy connection
by closing it (since close(), _getPC(), isOpen() and stmt.close() all
will synchronize on the (busy) physical connection.
I noticed this in a custom persistence layer, so I
Hello,
I noticed that with Oracle drivers you cannot kill a busy connection
by closing it (since close(), _getPC(), isOpen() and stmt.close() all
will synchronize on the (busy) physical connection.
I noticed this in a custom persistence layer, so I thought to check out
if DBCP handles this
