ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sven Boden (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Commented: (IBATIS-177) java.sql.SQLException: Result set already closed
Date Tue, 09 Aug 2005 16:18:35 GMT
    [ http://issues.apache.org/jira/browse/IBATIS-177?page=comments#action_12318181 ] 

Sven Boden commented on IBATIS-177:
-----------------------------------

Which kind of proofs it's not in iBATIS, but somewhere else. I found your problem at http://e-docs.bea.com/wls/docs70/faq/JTA.html#741271

You can shoot at BEA/Oracle for this, no change in iBATIS will fix this. they don't want you
executing queries from the client side.

So I guess this JIRA can be closed?

Regards,
Sven

> java.sql.SQLException: Result set already closed
> ------------------------------------------------
>
>          Key: IBATIS-177
>          URL: http://issues.apache.org/jira/browse/IBATIS-177
>      Project: iBatis for Java
>         Type: Bug
>   Components: SQL Maps
>     Versions: 2.1.0
>  Environment: windows environment, weblogic 8.1, oracle 9.i
>     Reporter: Gunaselan Varathan
>  Attachments: Main.java, RefTypeHandler.java, Test.java, hi.jsp, sql-map-config.xml,
test.sql, test.xml
>
> Hi, I am trying use oracle cursor. i implemented based on example given in Ibatis-53.
But i am getting forllowing error. an di dont whoe why it is happening.
> <Jul 29, 2005 10:54:00 AM EDT> <Error> <HTTP> <BEA-101017> <[ServletContext(id=4
> 929007,name=default,context-path=/default)] Root cause of ServletException.
> java.sql.SQLException: Result set already closed
>         at weblogic.jdbc.wrapper.ResultSet.checkResultSet(ResultSet.java:103)
>         at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:6
> 6)
>         at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImp
> l.next(Unknown Source)
>         at jsp_servlet.__hi._jspService(__hi.java:161)
>         at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
>         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
> (ServletStubImpl.java:1006)
>         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
> pl.java:419)
>         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
> pl.java:315)
>         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
> n.run(WebAppServletContext.java:6718)
>         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
> dSubject.java:321)
>         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
> 121)
>         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
> rvletContext.java:3764)
>         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
> pl.java:2644)
>         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
>         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message