> From: ma...@apache.org
> Subject: RE: dbcp pool evictor deadlock?
> Like a number of classes, PoolableConnection extends
> AbandonedTrace so this isn't entirely unexpected.
I really shouldn't be looking at code with a splitting headache...
- Chuck
THIS COM
Eric B. wrote:
>> "Caldarale, Charles R" wrote in message
>> news:0aae5ab84b013e45a7b61cb66943c172294795f...@usea-exch7.na.uis.unisys.com...
>>> From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B.
>>> Subject: dbcp pool evictor deadlock?
>>>
>>> THREAD 1:
>>> Name: Timer-1
>>> State: BLOC
>
> "Caldarale, Charles R" wrote in message
> news:0aae5ab84b013e45a7b61cb66943c172294795f...@usea-exch7.na.uis.unisys.com...
> > From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B.
> > Subject: dbcp pool evictor deadlock?
> >
> > THREAD 1:
> > Name: Timer-1
> > State: BLOCKED on
> > org.
> > I ran into the most troublesome deadlock over the weekend
> > on my server
>
> Always start by telling us what version of Tomcat (and therefore which
> commons-dbcp) you're using. It's likely commons-dbcp 1.2.2 since that's
> been out for a while, but the exact version may be critical.
Sor
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B.
> Subject: dbcp pool evictor deadlock?
>
> THREAD 1:
> Name: Timer-1
> State: BLOCKED on
> org.apache.tomcat.dbcp.dbcp.poolableconnect...@1e667871
> owned by: scheduling.QuartzInternal_Worker-0
> Total blocked: 1 Total waited: 15,342
>
Caldarale, Charles R wrote:
>> From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B.
>> Subject: dbcp pool evictor deadlock?
>>
>> I ran into the most troublesome deadlock over the weekend
>> on my server
>
> Always start by telling us what version of Tomcat (and therefore which
> commons-
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B.
> Subject: dbcp pool evictor deadlock?
>
> I ran into the most troublesome deadlock over the weekend
> on my server
Always start by telling us what version of Tomcat (and therefore which
commons-dbcp) you're using. It's likely commo
