You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Claus Köll (Jira)" <ji...@apache.org> on 2020/06/15 05:58:00 UTC
[jira] [Resolved] (JCR-4579) In rare situations we see "Closed
Statement; nested exception is java.sql.SQLException: Closed Statement"
[ https://issues.apache.org/jira/browse/JCR-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Köll resolved JCR-4579.
-----------------------------
Fix Version/s: 2.21.2
2.22
Resolution: Fixed
> 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
> Fix For: 2.22, 2.21.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)