Skip to content

Calling close() on WriteToInputStream before consuming all input causes upstream to timeout #3

@guss77

Description

@guss77

When streaming a large data source using WriteToInputStream, if the InputStream reader decides to close the stream early by calling close() - and does not perform any more read()s (as expected) - because the "closed" state cannot be propagated upstream due to Vert.x stream API limitations, the buffer will fill up until the upstream is paused and then gets stuck - no more data will be pulled from the upstream. If the upstream has a timeout, it may fire causing an error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions