[ http://issues.apache.org/jira/browse/DERBY-964?page=all ]
Myrna van Lunteren closed DERBY-964:
------------------------------------
Resolution: Cannot Reproduce
I cannot now remember why I logged this bug, and I don't see this occurring
anywhere now.
Maybe it was a failure on zOS only, but I'm usually better at specifying it
when a failure occurs on a specific hardware only. If it was on zOS, it's
probably been fixed by our actions to the client and to tests in the encoding
support changes. For instance DERBY-903 modified this test.
I'm marking this one as Cannot Reproduce.
> End of Stream prematurely reached error with DerbyNetClient
> -----------------------------------------------------------
>
> Key: DERBY-964
> URL: http://issues.apache.org/jira/browse/DERBY-964
> Project: Derby
> Type: Bug
> Components: Network Client
> Reporter: Myrna van Lunteren
> Fix For: 10.2.0.0
>
> When running the test store/streamingColumn with DerbyNetClient, the subtest
> for DERBY-500 fails with the following error:
> UNEXPECTED EXCEPTION - streams cannot be re-used but in case of varchar,
> stream is materialized the first time around. So multiple executions using
> streams should work fine.
> FAIL -- unexpected exception: java.sql.SQLException: End of Stream
> prematurely reached while reading Reader, parameter #4. Remaining data has
> been padded with 0x0.
> java.sql.SQLException: End of Stream prematurely reached while reading
> Reader, parameter #4. Remaining data has been padded with 0x0.
> This does not occur with embedded, nor with IBM Universal JDBC Driver (aka
> jcc/DerbyNet).
> derby.log shows truncation errors, not sure if this is the cause or not.
> Stack trace from .tmp:
> at
> org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:280)
> at
> org.apache.derby.client.am.PreparedStatement.executeUpdate(PreparedStatement.java:330)
> at
> org.apache.derbyTesting.functionTests.tests.store.streamingColumn.derby500_verifyVarcharStreams(streamingColumn.java(Compiled
> Code))
> at
> org.apache.derbyTesting.functionTests.tests.store.streamingColumn.main(streamingColumn.java:141)
> Caused by: org.apache.derby.client.am.SqlException: End of Stream prematurely
> reached while reading Reader, parameter #4. Remaining data has been padded
> with 0x0.
> at
> org.apache.derby.client.net.Request.writeScalarStream(Request.java(Compiled
> Code))
> at
> org.apache.derby.client.net.NetStatementRequest.buildEXTDTA(NetStatementRequest.java:884)
> at
> org.apache.derby.client.net.NetStatementRequest.writeExecute(NetStatementRequest.java:142)
> at
> org.apache.derby.client.net.NetPreparedStatement.writeExecute_(NetPreparedStatement.java:113)
> at
> org.apache.derby.client.am.PreparedStatement.writeExecute(PreparedStatement.java:1342)
> at
> org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:1580)
> at
> org.apache.derby.client.am.PreparedStatement.executeUpdateX(PreparedStatement.java:336)
> at
> org.apache.derby.client.am.PreparedStatement.executeUpdate(PreparedStatement.java:321)
> ... 2 more
> SQLSTATE(null):End of Stream prematurely reached while reading Reader,
> parameter #4. Remaining data has been padded with 0x0.
> SQLSTATE(null):End of Stream prematurely reached while reading InputStream,
> parameter #5. Remaining data has been padded with 0x0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
