[
https://issues.apache.org/jira/browse/DERBY-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348037#comment-16348037
]
Bryan Pendleton commented on DERBY-6981:
----------------------------------------
Attached 'patch1.diff' is a patch proposal, containing the proposed change to
TableScanResultSet.close as well as the reproduction script from this issue,
refactored into the UpdatableResultSetTest suite.
The test case fails without the change to TableScanResultSet.java, and passes
with it.
I haven't done any other testing (my environment is a bit flaky right now).
If this patch proposal seems like a reasonable path forward, I'll try to run
more tests.
> SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerExceptionXJ001.U
> ------------------------------------------------------------------
>
> Key: DERBY-6981
> URL: https://issues.apache.org/jira/browse/DERBY-6981
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.12.1.1
> Environment: OSX,CentOS
> Reporter: Roger Sanghee Kim
> Priority: Major
> Labels: newbie
> Attachments: Main.java, Test1.zip, derby-test.java, patch1.diff,
> test1.java
>
>
> Original error mesage:
>
> {code:java}
> java.sql.SQLException: DERBY SQL error: ERRORCODE: 0, SQLSTATE: XJ001,
> SQLERRMC: java.lang.NullPointerExceptionXJ001.U at
> org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown
> Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown
> Source) at org.apache.derby.client.am.ClientResultSet.next(Unknown Source) at
> org.ziptie.provider.credentials.internal.test1.main(test1.java:43) Caused by:
> ERROR XJ001: DERBY SQL error: ERRORCODE: 0, SQLSTATE: XJ001, SQLERRMC:
> java.lang.NullPointerExceptionXJ001.U at
> org.apache.derby.client.am.ClientResultSet.completeSqlca(Unknown Source) at
> org.apache.derby.client.net.NetResultSetReply.parseFetchError(Unknown Source)
> at org.apache.derby.client.net.NetResultSetReply.parseCNTQRYreply(Unknown
> Source) at org.apache.derby.client.net.NetResultSetReply.readFetch(Unknown
> Source) at org.apache.derby.client.net.ResultSetReply.readFetch(Unknown
> Source) at org.apache.derby.client.net.NetResultSet.readFetch_(Unknown
> Source) at org.apache.derby.client.net.NetResultSet.flowFetch(Unknown Source)
> at org.apache.derby.client.net.NetCursor.getMoreData_(Unknown Source) at
> org.apache.derby.client.am.Cursor.stepNext(Unknown Source) at
> org.apache.derby.client.am.Cursor.next(Unknown Source) at
> org.apache.derby.client.am.ClientResultSet.nextX(Unknown Source)
> {code}
> DERBY-6735 is very similar bug.
> DDL
>
> {code:java}
> CREATE TABLE TEST1
> (
> ID int PRIMARY KEY NOT NULL,
> LASTUPDATE timestamp
> ){code}
>
> I have attached test Code:[^derby-test.java]
> test Code with embeded derby : [^Main.java]
> ^Full code on my intellij : [^Test1.zip]:^
> Another database (PostgreSQL) has no problem.
> I also put a workaround in the code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
