[
https://issues.apache.org/jira/browse/DBCP-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764400#comment-16764400
]
Rahil S commented on DBCP-536:
------------------------------
[~garydgregory]
Sorry, let me put it in a better way. We don't interact directly with the
connection so we do not close it. Spring-JDBC does it for us. Here is the line
of spring-jdbc where the connection is released back to the pool -
https://github.com/spring-projects/spring-framework/blob/f7e53a071b8613ce9312d282770b29211da219b7/spring-jdbc/src/main/java/org/springframework/jdbc/core/JdbcTemplate.java#L339
> More than 5k+ instances of PgConnection created
> -----------------------------------------------
>
> Key: DBCP-536
> URL: https://issues.apache.org/jira/browse/DBCP-536
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Rahil S
> Priority: Major
> Attachments: Screenshot 2019-02-09 at 3.39.35 PM.jpg, Screenshot
> 2019-02-09 at 3.41.20 PM.jpg
>
>
> Hi,
>
> We are facing memory issues with DBCP2 in production. We are using the 2.0.1
> version of dbcp2. By analyzing heap dump we noticed that 5k+ instances of
> PgConnection were created. I have attached the screenshot of the same.
> We have set setMaxTotal(pool size) to 40 and initializing two BasicDatasource
> Objects for two different data source.
>
> Regards,
> Rahil
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
