Bug #19435 Operation not allowed after ResultSet closed
Submitted: 29 Apr 2006 12:49 Modified: 31 Mar 2014 11:47
Reporter: [ name withheld ] Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / J Severity:S1 (Critical)
Version:mysql 5.0 OS:Windows (windows xp sp2)
Assigned to: Alexander Soklakov CPU Architecture:Any

[29 Apr 2006 12:49] [ name withheld ]
Description:
As the title says. I try to do the following code and get this exception: java.sql.SQLException: Operation not allowed after ResultSet closed

I have no idea what's causing this. Can anyone help?

How to repeat:
ResultSet monster = query.executeQuery("select * from monsters where mIDnr="+ request.getParameter("Player"));
                ResultSet attacks = query.executeQuery("select a.* from attacks a, monstersattacks ma where  a.aIDnr = ma.aIDnr and ma.mIDnr="+ request.getParameter("Player"));
                
                out.println("test");
                out.println(monster.getString(0)); //<-- I get the exception here
                out.println("test");
[29 Apr 2006 13:00] Valeriy Kravchuk
Please, specify the exact MySQL server version and Connector/J version used.

Changed category to a more appropriate one.
[29 Apr 2006 13:05] [ name withheld ]
I used MySQL 5.0 Community Edition. The one without installer. Third from the top on this page http://dev.mysql.com/downloads/mysql/5.0.html

and as for Connector/J... it's this you mean right?
<context-param> 
        <param-name>jdbcDRIVER</param-name> 
        <param-value>org.gjt.mm.mysql.Driver</param-value>
        <!-- org.gjt.mm.mysql.Driver --> <!-- com.mysql.jdbc.Driver :connectorJ --> 
    </context-param> 

My apologies... I'm still a noob at mysql.
[9 May 2006 13:30] Tonci Grgin
Hi. Thanks for your problem report. Can you please check Reggie Burnett's post in http://bugs.mysql.com/bug.php?id=7248 and close this issue if that answers your question.
[9 Jun 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[31 Mar 2014 11:47] Alexander Soklakov
I close this report as "Can't repeat" because there is no feedback for a long time and codebase is too old. Please, feel free to reopen it if the problem still exists in current driver.