Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for user@commons.apache.org)
Message-ID: <5537351F.80605@elyograg.org>
Date: Tue, 21 Apr 2015 23:43:59 -0600
From: Shawn Heisey <apache@elyograg.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Commons Users List <user@commons.apache.org>
Subject: Re: [DBCP] Apparent deadlock related to getConnection
References: <552921C8.5020603@elyograg.org>	<55293434.5030906@gmail.com>
	<552A41B6.4060206@elyograg.org>	<552A8C4A.3050506@gmail.com>
	<552AAC0A.4060101@elyograg.org>	<552ABCBB.6060404@gmail.com>
	<552ADD4D.4050909@elyograg.org>
 <CALznzY7ajW1pz-Zf-c1qWn2z6ke_sU5+7wM0hvmQ=C1ftT32jw@mail.gmail.com>
 <5536E17A.6030106@elyograg.org> <5536EB26.10707@gmail.com>
In-Reply-To: <5536EB26.10707@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 4/21/2015 6:28 PM, Phil Steitz wrote:
> Thanks for providing the full stack traces, Shawn.  I assume the
> pool config is the same that you posted before, right?  Also, the
> mysql driver seems to be taking initiative to try to clean up
> abandoned connections itself.  That is holding some locks; but I
> don't see any deadlocks in the dumps.  I will look more at this
> later tonight.  I think it is possible there is a pool bug lurking
> in here.  One question: are you seeing connections fail validation? 
> I think you said you were testing on borrow / return.  Is that
> right?  Are you just letting the pool destroy the bad ones or are
> you destroying them yourself?

Thanks for your reply.

I have since learned that this was not an actual deadlock.  Somebody
dropped entries into the config database which asked my program to
reindex 56 million rows (nearly one third of the entire database) into
Solr.  That is not the kind of thing I intended that capability to
accomplish, because it takes WAY too long.

My program was working fine ... but sending watchdog alarms every
fifteen minutes because a "normal" cycle was taking hours longer than
expected.  I removed the reindex entries and restarted the program
instances, now everything is working fine again.

Thanks,
Shawn


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