Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Date: Sat, 25 Jul 2015 17:19:30 +0200
From: Bernd Eckenfels <ecki@zusammenkunft.net>
To: Phil Steitz <phil.steitz@gmail.com>
Cc: Commons Users List <user@commons.apache.org>
Subject: Re: [dbcp] Abandon Connection - not Logging in standalone
Message-ID: <20150725171930.00003a17.ecki@zusammenkunft.net>
In-Reply-To: <55B3A3F5.4080600@gmail.com>
References: <20150724011822.00000002.ecki@zusammenkunft.net>
	<55B2CB55.6000806@gmail.com>
	<20150725045458.000007ad.ecki@zusammenkunft.net>
	<55B3A3F5.4080600@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Am Sat, 25 Jul 2015 07:57:57 -0700
schrieb Phil Steitz <phil.steitz@gmail.com>:
> BasicDataSource allows you to directly set the abandoned connection
> log writer.  Your code uses PoolingDataSource, which requires you to
> configure the underlying object pool manually, so you need to use
> the setLogWriter method of the AbandonedConfig instance you use to
> configure the pool.

I tried that as well, but it did not help.

> Try looking at a thread dump.  Another possibility is that the
> evictor thread is hung waiting on a driver action.  

Thats why the output contains a thread dump, there the evictor thread
was idle.

I guess I would have to debug it.

Gruss
Bernd

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org