-
Notifications
You must be signed in to change notification settings - Fork 610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ieof packet referred to nonexistent channel #805
Comments
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 15, 2022
…isOpen and a Transport.write call Otherwise, a disconnect with a "packet referred to nonexistent channel" message can occur. This particularly happens when the transport.Reader thread passes an eof from the server to the ChannelInputStream, the reading library-user thread returns, and closes the channel at the same time as the transport.Reader thread receives the subsequent CHANNEL_CLOSE from the server.
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 16, 2022
…isOpen and a Transport.write call Otherwise, a disconnect with a "packet referred to nonexistent channel" message can occur. This particularly happens when the transport.Reader thread passes an eof from the server to the ChannelInputStream, the reading library-user thread returns, and closes the channel at the same time as the transport.Reader thread receives the subsequent CHANNEL_CLOSE from the server.
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 16, 2022
…isOpen and a Transport.write call Otherwise, a disconnect with a "packet referred to nonexistent channel" message can occur. This particularly happens when the transport.Reader thread passes an eof from the server to the ChannelInputStream, the reading library-user thread returns, and closes the channel at the same time as the transport.Reader thread receives the subsequent CHANNEL_CLOSE from the server.
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 16, 2022
…isOpen and a Transport.write call Otherwise, a disconnect with a "packet referred to nonexistent channel" message can occur. This particularly happens when the transport.Reader thread passes an eof from the server to the ChannelInputStream, the reading library-user thread returns, and closes the channel at the same time as the transport.Reader thread receives the subsequent CHANNEL_CLOSE from the server.
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 17, 2022
kegelh
added a commit
to kegelh/sshj
that referenced
this issue
Sep 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my project, I have logic like this:
However, this throws IOException "ieof packet referred to nonexistent channel", especially when connecting localhost and running in parallel after I upgrade sshj from 0.31 to 0.32.
The text was updated successfully, but these errors were encountered: