Skip to content
This repository has been archived by the owner on Apr 16, 2023. It is now read-only.

[🚧] ClosedChannelException in HTTP server after requests #32

Open
MarkL4YG opened this issue Jun 11, 2019 · 1 comment
Open

[🚧] ClosedChannelException in HTTP server after requests #32

MarkL4YG opened this issue Jun 11, 2019 · 1 comment
Assignees
Labels
blocked-3rd-party Feature or bug that is dependent on external changes and cannot progress further. bug Something isn't working feedback wanted Extra discussion is needed integration Related to integration with OS & other projects (external API)

Comments

@MarkL4YG
Copy link
Member

Describe the bug
When a request is sent to the HTTP server in the new REST integration a ClosedChannelException is thrown by Netty.

To Reproduce

  1. Send a request to the HTTP server.

Additional context
At the moment, it is not clear whether or not this impacts the result.
@finnWellers
Here is a gist of the log: https://gist.github.com/MarkL4YG/dc5d38fc9a5fb8987bab33dea498e558

@MarkL4YG MarkL4YG added bug Something isn't working feedback wanted Extra discussion is needed integration Related to integration with OS & other projects (external API) labels Jun 11, 2019
@finnWellers
Copy link
Contributor

A known Bug the Spark Framework: perwendel/spark#1101

@MarkL4YG MarkL4YG added the blocked-3rd-party Feature or bug that is dependent on external changes and cannot progress further. label Jun 11, 2019
@MarkL4YG MarkL4YG modified the milestone: Stable Release 1.1.0 Jun 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked-3rd-party Feature or bug that is dependent on external changes and cannot progress further. bug Something isn't working feedback wanted Extra discussion is needed integration Related to integration with OS & other projects (external API)
Development

No branches or pull requests

2 participants