Return-Path: 
 <issues-return-45866-apmail-commons-issues-archive=commons.apache.org@commons.apache.org>
X-Original-To: apmail-commons-issues-archive@minotaur.apache.org
Delivered-To: apmail-commons-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1C9EE10F17
	for <apmail-commons-issues-archive@minotaur.apache.org>;
 Tue, 27 Jan 2015 12:17:36 +0000 (UTC)
Received: (qmail 16885 invoked by uid 500); 27 Jan 2015 12:17:35 -0000
Delivered-To: apmail-commons-issues-archive@commons.apache.org
Received: (qmail 16694 invoked by uid 500); 27 Jan 2015 12:17:35 -0000
Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@commons.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@commons.apache.org>
List-Post: <mailto:issues@commons.apache.org>
List-Id: <issues.commons.apache.org>
Reply-To: issues@commons.apache.org
Delivered-To: mailing list issues@commons.apache.org
Received: (qmail 16451 invoked by uid 99); 27 Jan 2015 12:17:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2015 12:17:35 +0000
Date: Tue, 27 Jan 2015 12:17:35 +0000 (UTC)
From: "Benedikt Ritter (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12770298.1422349000000.183527.1422361055305@Atlassian.JIRA>
In-Reply-To: <JIRA.12770298.1422349000000@Atlassian.JIRA>
References: <JIRA.12770298.1422349000000@Atlassian.JIRA>
 <JIRA.12770298.1422349000012@arcas>
Subject: [jira] [Commented] (DBCP-431) SQLException: Error preloading the
 connection pool after upgrade to commons-dbcp2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/DBCP-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293419#comment-14293419 ] 

Benedikt Ritter commented on DBCP-431:
--------------------------------------

Hello [~scuenca],

the bug tracker is not a support forum. If you're having problems upgrading to the latest release, you'll probably be better of asking your question on the user mailing list (http://commons.apache.org/proper/commons-dbcp/mail-lists.html).

regards,
Benedikt

> SQLException: Error preloading the connection pool after upgrade to commons-dbcp2
> ---------------------------------------------------------------------------------
>
>                 Key: DBCP-431
>                 URL: https://issues.apache.org/jira/browse/DBCP-431
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Windows XP
> Junit 4.11
> Java 1.7
> Spring 4.0
> maven-compiler-plugin 3.2
> maven.surefire.plugin 2.17
> maven-cobertura-plugin 2.6
> Jenkins 1.549
>            Reporter: Sergio Cuenca
>            Priority: Minor
>              Labels: commons-dbcp2, connection-pooling
>
> Hi all,
> We have a continuous integration environment (Jenkins) to launch our JUnits tests.
> We had the version 1.4 of commons-dbcp to create the connection pools with Spring. The configuration was the following:
> {code:xml}
> <bean id="dataSourceTemplate" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
> 	  <property name="driverClassName"><value>${aplicacion.datasource.driverClassName}</value></property>
> 	  <property name="url"><value>${aplicacion.datasource.url}</value></property>
> 	  <property name="username"><value>${aplicacion.datasource.user}</value></property>
> 	  <property name="password"><value>${aplicacion.datasource.password}</value></property>
> 	  <property name="initialSize"><value>1</value></property>
> 	  <property name="maxActive"><value>15</value></property>
> 	  <property name="maxIdle"><value>2</value></property>
> 	  <property name="accessToUnderlyingConnectionAllowed"><value>${aplicacion.datasource.accessToUnderlyingConnectionAllowed}</value></property>
> 	</bean>
> {code}
> We use JUnit 4.11 and maven cobertura plugin 1.6. to launch the tests.
> This configuration was working CORRECTLY.
> After upgrade to commons-dbcp2, version 2.0.1. Some unit tests are reporting errors with the following message:
> java.sql.SQLException: Error preloading the connection pool.
> We launch one unit test each time, one by one. We create and destroy the connection pool every time.
> What can we do to solve this problem?? 
> Thank you very much.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)