[
https://issues.apache.org/jira/browse/ODE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559827#action_12559827
]
Alexey Ousov commented on ODE-229:
----------------------------------
I'm not a database expert :) I just tried to achieve stable work of ODE with
Oracle, and it is very-very tricky. I found an article which says that result
sets of pooled connections must be explicitly closed, and I thought it is rule.
> 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.
