cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <>
Subject [jira] [Assigned] (CXF-7831) SocketTimeoutException when previous response was exactly chunk length bytes
Date Mon, 03 Sep 2018 10:53:00 GMT


Freeman Fang reassigned CXF-7831:

    Assignee: Freeman Fang

> SocketTimeoutException when previous response was exactly chunk length bytes
> ----------------------------------------------------------------------------
>                 Key: CXF-7831
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.2.6
>            Reporter: Jan Hallonsten
>            Assignee: Freeman Fang
>            Priority: Major
>         Attachments: Check_endOfStream_before_suspending_input.patch,
> When using the Asynchronous Client HTTP Transport we get a SocketTimeout exception when
the previous response was exactly the same length as the chunk length by default 16320 bytes.
> After some investigation we have found that the problem is that when the http connection
is returned to PoolingNHttpClientConnectionManager the SelectionKey's interestOps does not
contain OP_READ. The input gets suspended in SharedInputBuffer when the buffer is full (16320
bytes by default) if this happens at the same time as the endOfStream is reached more input
is never requested. We have fixed it locally by adding an endOfStream check before suspending
input in SharedInputBuffer. This might not be the correct place to fix it since you could
argue that it should not be the responsibility of the user of PoolingNHttpClientConnectionManager
to return the http connection in the correct state.
> An example project to reproduce the problem is attached in and a patch
with our fix is in Check_endOfStream_before_suspending_input.patch

This message was sent by Atlassian JIRA

View raw message