[
https://issues.apache.org/jira/browse/DERBY-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081489#comment-13081489
]
Kristian Waagan commented on DERBY-5338:
----------------------------------------
There may be some relevant information in DERBY-2017 regarding exception
handling.
I believe that we now have the tools needed to avoid raising a protocol
exception (since Derby 10.6), but I don't know how much of the existing code
that would have to be changed.
> When attempting to insert a 4GB stream client gives SQLState XN015 network
> protocol error vs embedded 22003 data too large for type
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5338
> URL: https://issues.apache.org/jira/browse/DERBY-5338
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.9.0.0
> Reporter: Kathey Marsden
> Priority: Minor
>
> In converting LobLimits test DERBY-1903, I see that attempting to insert a
> 4GB stream with client gives the error XN015
> Caused by: org.apache.derby.client.am.SqlException: Network protocol error:
> the specified size of the InputStream, parameter #4, is less than the actual
> InputStream length.
> at
> org.apache.derby.client.net.Request.writePlainScalarStream(Request.java:359)
> at
> org.apache.derby.client.net.Request.writeScalarStream(Request.java:247)
> at
> org.apache.derby.client.net.NetStatementRequest.buildEXTDTA(NetStatementRequest.java:963)
> at
> org.apache.derby.client.net.NetStatementRequest.writeExecute(NetStatementRequest.java:151)
> at
> org.apache.derby.client.net.NetPreparedStatement.writeExecute_(NetPreparedStatement.java:174)
> at
> org.apache.derby.client.am.PreparedStatement.writeExecute(PreparedStatement.java:1800)
> at
> org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:2030)
> at
> org.apache.derby.client.am.PreparedStatement.executeUpdateX(PreparedStatement.java:417)
> at
> org.apache.derby.client.am.PreparedStatement.executeUpdate(PreparedStatement.java:403)
> ... 38 more
> vs's embedded's 22003, the length exceeds the maximum length for the data
> type.
> I am not sure if the connection is lost or not. It typically is with protocol
> errors.
> Look for this bug number in largedata.LobLimits.java for test case.
> You can remove the exclusion for usingDerbyNetClient and run
> org.apache.derbyTesting.functionTests.tests.largedata.LobLimitsLiteTest
> to reproduce the problem. I will check the test case in soon as part of
> DERBY-1903
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
