[
https://issues.apache.org/jira/browse/ODE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559567#action_12559567
]
Matthieu Riou commented on ODE-229:
-----------------------------------
Did you see any connection leak?
Normally the result set is closed with the connection anyway and as we're
running a transaction the connection from the pool is physically closed only at
transaction commit. So I doubt we have a leak here (and the simple scheduler
has been tested substantially).
> SimpleSheduler should close ResultSet
> -------------------------------------
>
> Key: ODE-229
> URL: https://issues.apache.org/jira/browse/ODE-229
> Project: ODE
> Issue Type: Bug
> Affects Versions: 1.1, 1.1.1, 1.2
> Environment: Windows XP Pro, JDK 1.5.0.07, Oracle 10g XE, Apache
> Tomcat 5.5.25
> Reporter: Alexey Ousov
> Priority: Minor
>
> ResultSet is not closed in function "List<String>
> org.apache.ode.scheduler.simple.JdbcDelegateFixed.getNodeIds()". It should be
> implicitly closed to avoid Database connection pool leaks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
