[
https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272237#comment-16272237
]
Paul King commented on GROOVY-8397:
-----------------------------------
Looking at the changes in that class over the time period you talk about, there
doesn't seem to be much that changed that could have the affect you describe.
We do query some extra metadata. That is know to sometimes throw exceptions for
some drivers which we carefully ignore. Perhaps though once that exception is
thrown, the connection might remain in a weird state and the cursor might
remain open. I'll try to prepare a snapshot version of Groovy where the extra
metadata checking defaults to not being queried. It might take a few days.
> ORA-01000: maximum open cursors exceeded
> ----------------------------------------
>
> Key: GROOVY-8397
> URL: https://issues.apache.org/jira/browse/GROOVY-8397
> Project: Groovy
> Issue Type: Bug
> Components: SQL processing
> Affects Versions: 2.4.9, 2.4.10, 2.4.11, 2.4.12, 2.4.13
> Environment: Oracle 12.1.0.2.0
> Java 8 64bit
> Reporter: mgroovy
> Labels: cursor, oracle, sql
>
> * Evolving Oracle 12.1.0.2.0 DB schema with many objects from Groovy code
> based on Groovy Sql class worked up to groovy-2.4.7
> * From 2.4.9 up to 2.4.13 after some time during table creation/update schema
> evolver throws
> {code}
> java.sql.SQLException: ORA-01000: Maximale Anzahl offener Cursor überschritten
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
