db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4519) Infinite loop in StreamFileContainer.writeColumn
Date Wed, 20 Jan 2010 12:20:54 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802807#action_12802807

Knut Anders Hatlen commented on DERBY-4519:

Thanks, Kristian. The patch looks good. +1

> Infinite loop in StreamFileContainer.writeColumn
> ------------------------------------------------
>                 Key: DERBY-4519
>                 URL: https://issues.apache.org/jira/browse/DERBY-4519
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:,,,,,,
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>             Fix For:
>         Attachments: derby-4519-1a-argument_swap.diff, derby-4519-2a-infinite_loop_fixes.diff
> The offset and length argument have been swapped in the calls to InputStream.read(byte,offset,
length) and write(byte,offset, length). This code is inside a do-while (true) loop, and the
only normal way out is when InputStream.read returns -1. This will never happen since the
stream is asked to read zero bytes. Derby ends up eating up all available CPU, limited to
a single core / CPU.
> The bug hasn't been observed because Derby is materializing all values when calling this
code. Enabling streaming capabilities in the sorter revealed it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message