This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 223768 - com.ibm.db2.jcc.b.SqlException: [jcc][t4][10120][10898][3.50.152] Ugyldig operasjon: result set er lukket. ERRORCODE=-4470, SQLSTATE=null
Summary: com.ibm.db2.jcc.b.SqlException: [jcc][t4][10120][10898][3.50.152] Ugyldig ope...
Status: RESOLVED DUPLICATE of bug 223729
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-13 12:53 UTC by viggonavarsete
Modified: 2012-12-13 13:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 171186


Attachments
stacktrace (824 bytes, text/plain)
2012-12-13 12:53 UTC, viggonavarsete
Details

Note You need to log in before you can comment on or make changes to this bug.
Description viggonavarsete 2012-12-13 12:53:48 UTC
Build: NetBeans IDE Dev (Build 201211200002)
VM: Java HotSpot(TM) Client VM, 20.7-b02, Java(TM) SE Runtime Environment, 1.6.0_32-b05
OS: Windows 7

User Comments:
viggonavarsete: Trying to select from a DB2 table after I did a delete of two rows (which also made Netbeans crash)

viggonavarsete: Trying to delete two rows from the resultset of a query towards a DB2 database when it crached.




Stacktrace: 
com.ibm.db2.jcc.b.SqlException: [jcc][t4][10120][10898][3.50.152] Ugyldig operasjon: result set er lukket. ERRORCODE=-4470, SQLSTATE=null
   at com.ibm.db2.jcc.b.wc.a(wc.java:55)
   at com.ibm.db2.jcc.b.wc.a(wc.java:102)
   at com.ibm.db2.jcc.b.jk.Bb(jk.java:3987)
   at com.ibm.db2.jcc.b.jk.c(jk.java:273)
   at com.ibm.db2.jcc.b.jk.next(jk.java:258)
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper.loadDataFrom(SQLExecutionHelper.java:611)
Comment 1 viggonavarsete 2012-12-13 12:53:50 UTC
Created attachment 129315 [details]
stacktrace
Comment 2 Jaroslav Havlin 2012-12-13 13:25:02 UTC

*** This bug has been marked as a duplicate of bug 223729 ***