[
https://issues.apache.org/jira/browse/JCR-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153508#comment-17153508
]
Julian Reschke edited comment on JCR-4579 at 12/1/20, 10:37 AM:
----------------------------------------------------------------
trunk: (2.21.2) [r1878846|http://svn.apache.org/r1878846]
2.20: (2.20.2) [r1879638|http://svn.apache.org/r1879638]
2.16: [r1883981|http://svn.apache.org/r1883981]
was (Author: reschke):
trunk: (2.21.2) [r1878846|http://svn.apache.org/r1878846]
2.20: [r1879638|http://svn.apache.org/r1879638]
> jackrabbit-data: allow to disable statement pooling through system property
> ---------------------------------------------------------------------------
>
> Key: JCR-4579
> URL: https://issues.apache.org/jira/browse/JCR-4579
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-data
> Reporter: Claus Köll
> Assignee: Claus Köll
> Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.22, 2.16.7, 2.21.2, 2.20.2
>
>
> We are using a DriverDataSource and in really rare situations we see
> following exception
> {code:java}
> Closed Statement; nested exception is java.sql.SQLException: Closed Statement
> {code}
> The DriverDataSource uses the commons-dbcp library to create a
> BasicDataSource.
> The old commons-dbcp is also using a fairly old version of commons-pool.
> After researching a valid fix can be is to disable the pooling of
> PreparedStatements.
> As a quick fix i would define a SystemProperty to disable the pooling. We
> have a really high load and we see no performance impacts.
> As a future fix we can update to a actual dbcp2 version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
