Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <56650B84.7080107@gmail.com>
References: 
 <CAJNYKDs52VUyh2z8f9PAay31e-ezvat-dnepcr5zZ5mX6tdY_w@mail.gmail.com>
	<56650B84.7080107@gmail.com>
Date: Mon, 7 Dec 2015 10:50:26 -0700
Message-ID: 
 <CAJNYKDv9xqSEVTV5TKFUg9e2bOgm1t-vcXea8kZ0J_+jPojuYA@mail.gmail.com>
Subject: Re: [dbcp] JMX mbean doesn't exist after upgrade to 2.1/2.1.1
From: Anthony Biacco <abiacco@handll.com>
To: Commons Users List <user@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a11443d7efda7010526527d78

--001a11443d7efda7010526527d78
Content-Type: text/plain; charset=UTF-8

On Sun, Dec 6, 2015 at 9:31 PM, Phil Steitz <phil.steitz@gmail.com> wrote:

> On 12/5/15 2:07 AM, Anthony Biacco wrote:
> > I was running dbcp 2.0.1 with pool 2.4.2.
> > I updated dbcp to 2.1 and the mbean org.apache.commons.pool2 doesn't
> exist
> > anymore. 2.1.1 is a no-go as well
> > I'm running under Tomcat 8.0.28
> >
> > Could this have to do with:
> https://issues.apache.org/jira/browse/DBCP-434 ?
>
> Yes, as of DBCP 2.1, you need to specify a jmxName in order for the
> pool (and statement pools) to be registered with JMX.
> Unfortunately, the bug being tracked now as DBCP-452 makes
> specification of the jmxName property in a JNDI resource definition
> ineffective.  Once 2.2 is released with the fix for DBCP-452, you
> will be able to specify a jmxName property and the pool will
> register itself under that name.
>
> Phil
>
>
Thanks, i'll downgrade while waiting for the new version.

-Tony

--001a11443d7efda7010526527d78--