Re: [dbcp] JMX mbean doesn't exist after upgrade to 2.1/2.1.1

[Phil Steitz]

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
>
> Example of one of my resources is:
>
>  name="jdbc/NAME" auth="Container"
> type="javax.sql.DataSource"
> factory="org.apache.commons.dbcp2.BasicDataSourceFactory"
> username="USERNAME"
> password="PASSWORD"
> driverClassName="com.mysql.jdbc.Driver"
> url="URL"
> initialSize="5"
> minIdle="5"
> maxIdle="20"
> maxTotal="50"
> maxWaitMillis="4000"
> testOnBorrow="true"
> testWhileIdle="true"
> blockWhenExhausted="true"
> numTestsPerEvictionRun="20"
> timeBetweenEvictionRunsMillis="12"
> softMinEvictableIdleTimeMillis="119000"
> minEvictableIdleTimeMillis="-1"
> validationQuery="/* ping */"
> validationQueryTimeout="2"
> removeAbandoned="true"
> removeAbandonedOnBorrow="true"
> removeAbandonedTimeout="60"
> logAbandoned="true"
> />
>
> Thanks,
>
> -Tony
>


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

[ANNOUNCEMENT] Commons Configuration 2.0-beta2 Released

[Oliver Heger]

The Apache Commons Team is pleased to announce the availability of
Apache Commons Configuration 2.0-beta2.

The Commons Configuration software library provides a generic
configuration interface which enables an application to read
configuration data from a variety of sources.

This is another beta release incorporating some minor API changes in
reaction to community feedback. Hopefully the API is stabilizing towards
the final 2.0 release.

Version 2 is a major redesign of the Configuration API.
It breaks compatibility in many areas and, therefore, is not a drop-in
replacement for Commons Configuration 1.x. The main purpose of this
series of alpha and beta releases is to gather feedback from the
community about the reworked API. IT IS NOT YET PRODUCTION READY. There
may still be some changes on the public API.

A full list of all changes can be found in the release notes at
  http://www.apache.org/dist/commons/configuration/RELEASE-NOTES.txt

There is also an upgrade guide available for users of version 1.x at
  http://commons.apache.org/configuration/userguide/upgradeto2_0.html

Source and binary distributions are available for download from the
Apache Commons download site:

http://commons.apache.org/proper/commons-configuration/download_configuration.cgi

When downloading, please verify signatures using the KEYS file available
at the above location when downloading the release. (Note: Because this
is a beta version, we decided that it will not be distributed to Maven
central.)

For complete information on Commons Configuration, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons Configuration website:

http://commons.apache.org/proper/commons-configuration/

Oliver Heger, on behalf of the Apache Commons community

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