[
https://issues.apache.org/jira/browse/JCR-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130774#comment-17130774
]
Julian Reschke commented on JCR-4579:
-------------------------------------
That said, any chance you can do this without affecting the published API? Does
the variable need to be public?
> In rare situations we see "Closed Statement; nested exception is
> java.sql.SQLException: Closed Statement"
> ---------------------------------------------------------------------------------------------------------
>
> 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
>
> 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)
