[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    [jira] [Closed] (DBCP-470) Create a new BasicDataSource, the database hasn't start, the DBCP's pool 
From:       "Gary D. Gregory (Jira)" <jira () apache ! org>
Date:       2023-01-30 23:45:00
Message-ID: JIRA.12999884.1472091291000.22016.1675122300096 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/DBCP-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Gary D. Gregory closed DBCP-470.
--------------------------------
    Resolution: Information Provided

> Create a new BasicDataSource, the database hasn't start, the DBCP's pool will be \
>                 leaked
> ---------------------------------------------------------------------------------------
>  
> Key: DBCP-470
> URL: https://issues.apache.org/jira/browse/DBCP-470
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: All environment
> Reporter: jeho0815
> Priority: Major
> Labels: robustness, security
> Fix For: 1.4.1
> 
> Original Estimate: 4h
> Remaining Estimate: 4h
> 
> First the database hasn't start, then create a new BasicDataSource.  The method \
> createDataSource judge dataSource == null, will create a new dataSource. The first \
> step is create a connectionPool, second create a connectionFactory, but \
> validateConnectionFactory will throw a SQLNestedException, the dataSource will be \
> null again. Next itme repeat the steps again and again. The most import issue is \
> create the connectionPool will be refered by a java.lang.Timer, so it can't be \
> collected by GC. If the minIdle is positive, when database status is ok, it will \
> create connection also. As a word, the bug will cause memory leak and may cause \
> connection leak.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[prev in list] [next in list] [prev in thread] [next in thread]