db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1510) 'SQLBinary.readFromStream' can enter endless loop
Date Thu, 27 Jul 2006 21:57:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1510?page=all ]

Kristian Waagan updated DERBY-1510:

    Attachment: derby-1510-1a.diff

'derby-1510-1a.diff' makes sure derby does not enter an endless loop if InputStream.available()
returns 0 and we have already filled the buffer. Before, it was possible to start looping
with a read(byte[], pos, 0) call (my laptop used 100% CPU for nearly 29 hours because of this...).

The fix is minimal. If anyone wants to rewrite more of the method, please do so.

Please review/commit the patch.

> 'SQLBinary.readFromStream' can enter endless loop
> -------------------------------------------------
>                 Key: DERBY-1510
>                 URL: http://issues.apache.org/jira/browse/DERBY-1510
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, SQL
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-1510-1a.diff
> Under certain circumstances, the method 'SQLBinary.readFromStream' can enter an endless
loop while reading the stream. The following must be true for the bug to occur: 
>  * There must be more data in the stream than what can fit into the initial buffer (32
>  * The method 'available' of the stream returns 0.
> Since the default return value for 'InputStream.available' is 0, and the method reading
the stream can be used for data types CHAR FOR BIT DATA, VARCHAR FOR BIT DATA and LONG VARCHAR
FOR BIT DATA, the bug should be fixed. The maximum length is 32700 bytes.
> The method will also be used by SQLBlob, but it may be better to introduce a new streaming
method for it, since the current implementation has memory-problems for large data (materializes
the whole stream). A separate issue should/will be created for this.
> The symptom for this bug is a hang when calling one of the execute methods of Prepared-
or CallableStatement and maybe also certain set methods in ResultSet.
> The visibility of this bug is very low, but the impact is severe/critical. When the JDBC
4 length less streaming overloads are added (DERBY-1417), visibility might increase.

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


View raw message