Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 15 Jul 2011 17:36:00 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2078195969.18086.1310751360625.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DERBY-5338) When attempting to insert a 4GB
 stream client gives SQLState XN015 network protocol error vs embedded 22003
 data too large for type
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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