[#PETALSSEKPI-31] PooledDataSources not closed - Petals Link JIRA

Details

Type: Bug
Status: New
Priority: Minor
Resolution: Unresolved
Affects Version/s: 1.1.1
Fix Version/s: None
Component/s: None
Security Level: Public

Description:

Hide

The se-kpi with the c3p0 pool (latest versions) sometimes print a warn:

12:40:57,500  WARN com.mchange.v2.c3p0.management.ActiveManagementCoordinator:56 - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources.

Doctor, will I live?

Show

The se-kpi with the c3p0 pool (latest versions) sometimes print a warn:

12:40:57,500  WARN com.mchange.v2.c3p0.management.ActiveManagementCoordinator:56 - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources.

Doctor, will I live?

Environment:

RHEL 5, esb 3.1.1

Activity

Ascending order - Click to sort in descending order

Frédéric Gardes made changes - Wed, 18 May 2011 - 12:48:27 +0200

Field	Original Value	New Value
Description	The se-kpi with the c3p0 pool (latest versions) sometimes print a warn: {note} 12:40:57,500 WARN com.mchange.v2.c3p0.management.ActiveManagementCoordinator:56 - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources. {note} Doctor, will I live?	The se-kpi with the c3p0 pool (latest versions) sometimes print a warn: {code} 12:40:57,500 WARN com.mchange.v2.c3p0.management.ActiveManagementCoordinator:56 - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources. {code} Doctor, will I live?
Priority		Minor [ 4 ]

Hide

Permalink

Frédéric Gardes added a comment - Wed, 18 May 2011 - 15:38:31 +0200

I found something very interesting:

I'm using a MySQL database for the se kpi:

############
### SE-KPI properties
############

##Globals Informations
jdbc.hibernate.hbm2ddl.auto = update
jdbc.hibernate.show_sql = false

##C3P0 Informations
c3po.acquireIncrement = 1
c3po.minPoolSize = 5
c3po.maxPoolSize = 100
c3po.acquireRetryAttempts = 10
c3po.maxIdleTime = 50
c3po.idleConnectionTestPeriod = 30

## MySQL Datasource
jdbc.driverClassName=com.mysql.jdbc.Driver
jdbc.url=jdbc:mysql://rose-mybdm:3306/petals
jdbc.username=petals
jdbc.password=petals
jdbc.hibernate.dialect=com.ebmwebsourcing.petalsview.persistence.util.MySqlInnoDBDialect

I'm using a MySQL database for the registry:

#To use mySQL
registry.db.driver=com.mysql.jdbc.Driver
registry.db.url=jdbc:mysql://rose-mybdm:3306/petals
registry.db.password=petals
registry.db.user=petals
registry.db.dialect=org.hibernate.dialect.MySQLInnoDBDialect
registry.db.caching.enabled=false
registry.db.c3p0.enabled=true

If I deactivate the c3p0 of the registry, I haven't got the error into the logs. If I activate it, I've got the error:

registry.db.c3p0.enabled=true

So it seems that the 2 hibernate c3p0 configurations...aren't isolated .

Show

Frédéric Gardes added a comment - Wed, 18 May 2011 - 15:38:31 +0200 I found something very interesting: I'm using a MySQL database for the se kpi:

############
### SE-KPI properties
############

##Globals Informations
jdbc.hibernate.hbm2ddl.auto = update
jdbc.hibernate.show_sql = false

##C3P0 Informations
c3po.acquireIncrement = 1
c3po.minPoolSize = 5
c3po.maxPoolSize = 100
c3po.acquireRetryAttempts = 10
c3po.maxIdleTime = 50
c3po.idleConnectionTestPeriod = 30

## MySQL Datasource
jdbc.driverClassName=com.mysql.jdbc.Driver
jdbc.url=jdbc:mysql://rose-mybdm:3306/petals
jdbc.username=petals
jdbc.password=petals
jdbc.hibernate.dialect=com.ebmwebsourcing.petalsview.persistence.util.MySqlInnoDBDialect

I'm using a MySQL database for the registry:

#To use mySQL
registry.db.driver=com.mysql.jdbc.Driver
registry.db.url=jdbc:mysql://rose-mybdm:3306/petals
registry.db.password=petals
registry.db.user=petals
registry.db.dialect=org.hibernate.dialect.MySQLInnoDBDialect
registry.db.caching.enabled=false
registry.db.c3p0.enabled=true

If I deactivate the c3p0 of the registry, I haven't got the error into the logs. If I activate it, I've got the error:

registry.db.c3p0.enabled=true

So it seems that the 2 hibernate c3p0 configurations...aren't isolated

.

Petals SE KPI

PooledDataSources not closed

Details

Activity

People

Dates