[
https://issues.apache.org/jira/browse/IBATIS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537228
]
vishakha sawant commented on IBATIS-350:
----------------------------------------
I am facing one more issue regarding cursor only. It's somewhat similar with
the above issue but In this issue I am getting exception while retrieving
values from resultset so do we have any other way to handle this situation as
because of this I am not able to retrieve the next parameter from stored
procedure.
> cursor is closed exception not handled in iBatis
> ------------------------------------------------
>
> Key: IBATIS-350
> URL: https://issues.apache.org/jira/browse/IBATIS-350
> Project: iBatis for Java
> Issue Type: Bug
> Components: SQL Maps
> Affects Versions: 2.1.7
> Environment: jboss-4.0.3SP1, Spring 1.2.6, Oracle 10G driver-
> ojdbc14.jar
> Reporter: vishakha sawant
>
> Hi
> I posted this issue in IBATIS-53 on 12 july 2006 but i didnt received any
> replies so I am creating new jira issue for the same
> please reply me as soon as possible because it is very urgent
> We are using a patch version iBatis for REF CURSOR. We are using legacy
> database
> we are getting exception "Cursor is closed" while executing a procedure.
> stack trace of that exception is
> java.sql.SQLException : Cursor is closed.
> at
> oracle.jdbc.driver.T4CResultSetAccessor.getCursor(T4CResultSetAccessor.java:271)
> at
> oracle.jdbc.driver.ResultSetAccessor.getObject(ResultSetAccessor.java:94)
> at oracle.jdbc.driver.OracleCallableStatement.getObject
> (OracleCallableStatement.java:1368)
> at test.TestSPA.main(TestSPA.java:95)
> After doing some R&D I found that the if cursor is 'OUT' parameter and that
> is not opened in procedure, it will result in this exception. According to
> stack trace I found that in retrieveOutputParameters() method of
> com.ibatis.sqlmap.engine.execution.SqlExecutor.java cs.getObject(i+1) is
> causing this exception. For a time being we are catching that exception so
> that we can retrieve other OUT values from procedure. Is there any other way
> to resolve this issue?
> It's urgent.
> Regards,
> Vishakha Sawant
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
