[jira] [Created] (FLINK-33014) flink jobmanager raise java.io.IOException: Connection reset by peer

2023-08-31 Thread zhu (Jira)
zhu created FLINK-33014: --- Summary: flink jobmanager raise java.io.IOException: Connection reset by peer Key: FLINK-33014 URL: https://issues.apache.org/jira/browse/FLINK-33014 Project: Flink Issue

[jira] [Created] (FLINK-21952) Make all the "Connection reset by peer" exception wrapped as RemoteTransportException

2021-03-24 Thread Yun Gao (Jira)
Yun Gao created FLINK-21952: --- Summary: Make all the "Connection reset by peer" exception wrapped as RemoteTransportException Key: FLINK-21952 URL: https://issues.apache.org/jira/browse/FLINK-21952

[jira] [Created] (FLINK-21334) Run kubernetes pyflink application test fails with Connection reset by peer on setup

2021-02-09 Thread Piotr Nowojski (Jira)
Piotr Nowojski created FLINK-21334: -- Summary: Run kubernetes pyflink application test fails with Connection reset by peer on setup Key: FLINK-21334 URL: https://issues.apache.org/jira/browse/FLINK-21334

[jira] [Created] (FLINK-19925) Errors$NativeIoException: readAddress(..) failed: Connection reset by peer

2020-11-02 Thread godfrey he (Jira)
godfrey he created FLINK-19925: -- Summary: Errors$NativeIoException: readAddress(..) failed: Connection reset by peer Key: FLINK-19925 URL: https://issues.apache.org/jira/browse/FLINK-19925 Project

[jira] [Created] (FLINK-19705) Avro Confluent Schema Registry nightly end-to-end test: curl: (56) Recv failure: Connection reset by peer

2020-10-18 Thread Robert Metzger (Jira)
Robert Metzger created FLINK-19705: -- Summary: Avro Confluent Schema Registry nightly end-to-end test: curl: (56) Recv failure: Connection reset by peer Key: FLINK-19705 URL: https://issues.apache.org/jira/browse

Re: Connection reset by peer

2015-11-15 Thread Gyula Fóra
> trace was *exactly > *the same but it was from the web interface, and was due to the *connection > reset by peer *]. Currently, the web interface does not handle > exceptionCaught events cleanly. > One of my PRs has addressed this by adding a exception handler at the end > of pi

Re: Connection reset by peer

2015-11-15 Thread Sachin Goel
I used to get a similar exception [I do not remember if the stack trace was *exactly *the same but it was from the web interface, and was due to the *connection reset by peer *]. Currently, the web interface does not handle exceptionCaught events cleanly. One of my PRs has addressed this by adding

Re: Connection reset by peer

2015-11-15 Thread Ufuk Celebi
ally means the last handler in the > pipeline did not handle the exception. > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > at sun.nio.c

Re: Connection reset by peer

2015-11-14 Thread Ufuk Celebi
15:37:49,905 WARN io.netty.channel.DefaultChannelPipeline > - An exceptionCaught() event was fired, and it reached at > the tail of the pipeline. It usually means the last handler in the > pipeline did not handle the exception. > java.io.IOException: Connection reset by peer > at su

Connection reset by peer

2015-11-14 Thread Gyula Fóra
means the last handler in the pipeline did not handle the exception. java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer