getBlobLength causes ArrayIndexOutOfBounds Exception [JDBC153] #195
Comments
|
Commented by: Roman Rokytskyy (rrokytskyy) I have fixed the ArrayIndexOutBoundsException, now the normal SQLException should be thrown. The line you have provided means that server did not return us any data when asking a blob length, that is an error condition for us (so exception should be thrown anyway). However, I have noticed that the line numbers for some classes diverge a lot compared to the current HEAD. I do not remember to change the sources there so much. Can you please check the JDBC driver version, please. Please also re-open the issue as soon as you get any chance to make the issue reproducable... |
Modified by: Roman Rokytskyy (rrokytskyy)Version: Jaybird 2.2 [ 10053 ] Fix Version: Jaybird 2.2 [ 10053 ] timeestimate: 0 [ 0 ] timeoriginalestimate: 0 [ 0 ] |
Modified by: Roman Rokytskyy (rrokytskyy)status: Open [ 1 ] => Resolved [ 5 ] resolution: Incomplete [ 4 ] |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Stefan Schmaltz (schlocke)
Assigned to: Roman Rokytskyy (rrokytskyy)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
at org.firebirdsql.gds.impl.GDSHelper.getBlobLength(GDSHelper.java:567)
at org.firebirdsql.jdbc.field.FBBlobField.getBytesInternal(FBBlobField.java:127)
at org.firebirdsql.jdbc.field.FBBlobField.getCachedObject(FBBlobField.java:176)
at org.firebirdsql.jdbc.FBCachedFetcher.<init>(FBCachedFetcher.java:117)
at org.firebirdsql.jdbc.AbstractResultSet.<init>(AbstractResultSet.java:137)
at org.firebirdsql.jdbc.FBResultSet.<init>(FBResultSet.java:19)
at org.firebirdsql.jdbc.AbstractStatement.getResultSet(AbstractStatement.java:622)
at org.firebirdsql.jdbc.AbstractStatement.getResultSet(AbstractStatement.java:603)
at org.firebirdsql.jdbc.AbstractPreparedStatement.executeQuery(AbstractPreparedStatement.java:170)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76)
... 31 more
This problem is not reproduceable, it happens sometimes without special conditions. Maybe this is a multithreading-Issue? If yes, how can we avoid it?
Commits: 2bfc6e7
The text was updated successfully, but these errors were encountered: