[jira] [Commented] (DERBY-6456) Infinite loop in NetworkServerControlImpl when reply >= 32k

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen commented on DERBY-6456:
-------------------------------------------

This may be a fallout from DERBY-5236, which changed DDMWriter.writeLDString() so that the maximum message length was increased from ~32KB to 64KB. The client driver was adjusted accordingly, but it seems like we overlooked that NetworkServerControl also could act as a client, and DDMReader still only allocates a large enough buffer to hold ~32KB.

> Infinite loop in NetworkServerControlImpl when reply >= 32k
> -----------------------------------------------------------
>
>                 Key: DERBY-6456
>                 URL: https://issues.apache.org/jira/browse/DERBY-6456
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.10.1.1
>            Reporter: Martin JANDA
>
> When size of reply in NetworkServerControlImpl  equals to 32k (max size for short) ensureDataInBuffer is in infinite loop. clientIs.read(..., replyBuffer.length - replyBufferCount) return 0 because 'replyBuffer.length - replyBufferCount' is 0 (bytes to read).
> Steps to reproduce:
> Open many connections (for me 34) with at least 1 SELECT query. and call getRuntimeInfo(). Runtime info string.length > 32kB. Leading to infinite loop.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)