You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm calling ChannelSftp.cd(Path) on a session that has a timeout of five seconds, then make sure that the SFTP-Server does not answer, but also does not break the connection. The execution of the client hangs in the read loop of the PipedInputStream:
java.lang.Thread.State: WAITING
at java.lang.Object.wait(Object.java:-1)
at java.io.PipedInputStream.read(PipedInputStream.java:326)
at java.io.PipedInputStream.read(PipedInputStream.java:377)
at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2866)
at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2894)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2149)
at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:331)
at my.App.changeDirViaSftp(SftpProvider.java:621)
(You mostly catch it in the wait if you pause the thread, but it really loops the whole time). It seems that it can't be easily helped, since the PipedInputStream does not implement any timeout.
I would expect the timeout to have some effect
The text was updated successfully, but these errors were encountered:
I'm calling ChannelSftp.cd(Path) on a session that has a timeout of five seconds, then make sure that the SFTP-Server does not answer, but also does not break the connection. The execution of the client hangs in the read loop of the PipedInputStream:
java.lang.Thread.State: WAITING
at java.lang.Object.wait(Object.java:-1)
at java.io.PipedInputStream.read(PipedInputStream.java:326)
at java.io.PipedInputStream.read(PipedInputStream.java:377)
at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2866)
at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2894)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2149)
at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:331)
at my.App.changeDirViaSftp(SftpProvider.java:621)
(You mostly catch it in the wait if you pause the thread, but it really loops the whole time). It seems that it can't be easily helped, since the PipedInputStream does not implement any timeout.
I would expect the timeout to have some effect
The text was updated successfully, but these errors were encountered: