[
https://issues.apache.org/jira/browse/CONNECTORS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571297#comment-13571297
]
Karl Wright commented on CONNECTORS-638:
----------------------------------------
It's worth noting that I think it is impossible for the bug here to be in
either PostgreSQL or the PostgreSQL JDBC driver. The only way it can occur is
by miscounting handles that we have successfully allocated already. So it is
either in the pool code (which is suspicious because it was new in ManifoldCF
1.0), or in one or two particular kinds of SQL transactions.
A careful audit of the connection pool code should thus be done. Since I've
already done this more than once, another pair of eyes might be useful...
> Possible leakage of database connection handles
> -----------------------------------------------
>
> Key: CONNECTORS-638
> URL: https://issues.apache.org/jira/browse/CONNECTORS-638
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 1.0, ManifoldCF 1.0.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Critical
> Fix For: ManifoldCF 1.2
>
>
> Reports of a leak of connection handles, shown because ManifoldCF winds up
> waiting to get a connection, and failing.
> The database in question so far always seems to be PostgreSQL, FWIW, and it
> has been proven that there is a connection handle leak, so that all the
> crawler threads are eventually waiting for non-existent connection handles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
