[
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962756#comment-16962756
]
Anudeep edited comment on SSHD-952 at 10/30/19 7:20 AM:
--------------------------------------------------------
Hi [~lgoldstein],
I believe timeout was introduced to unblock the threads ,in previous versions
if there is no space thread was waiiting and if there is closure due to some
invalid chunk of data from client thread was blocked for ever and now with new
implementation at-least thread gets released after some timeout.
We have seen a case in previous versions if there are 3 blocked threads no new
session was served as threads are exhausted.
I want to understand if current logic will close the client session if the
threads gets timed out or will it keep open until it free some space on the
channel?
Regards,
Anudeep
was (Author: anudeepgangasani):
Hi [~lgoldstein],
I believe timeout was introduced to unblock the threads ,in previous versions
if there is no space thread was blocked for ever and now with new
implementation at-least thread gets released after some timeout.
We have seen a case in previous versions if there are 3 blocked threads no new
session was served as threads are exhausted.
I want to understand if current logic will close the client session if the
threads gets timed out or will it keep open until it free some space on the
channel?
Regards,
Anudeep
> What is the expected behavior of waitForSpace(long millis) method on default
> timeout of 30 seconds
> --------------------------------------------------------------------------------------------------
>
> Key: SSHD-952
> URL: https://issues.apache.org/jira/browse/SSHD-952
> Project: MINA SSHD
> Issue Type: Question
> Affects Versions: 2.2.0
> Reporter: Anudeep
> Priority: Major
>
> Hi Team,
> Can you please let us know the expected behavior of waitForSpace(long millis)
> method of Window.java class . As per our test we see on timeout thread get
> released and it spawns a new thread on timeout. Is this an expected behavior ?
> 2019-10-24 12:33:26,123 DEBUG [org.apache.sshd.server.channel.ChannelSession]
> (Thread-44 (HornetQ-client-global-threads-407809182))
> flush(ChannelOutputStream[ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]]
> SSH_MSG_CHANNEL_DATA) failed (SocketTimeoutException) to wait for space of
> len=1190: waitForCondition(Window[server/remote](ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]))
> timeout exceeded: 20000
> 2019-10-24 12:33:46,126 DEBUG [org.apache.sshd.server.channel.ChannelSession]
> (Thread-44 (HornetQ-client-global-threads-407809182))
> flush(ChannelOutputStream[ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]]
> SSH_MSG_CHANNEL_DATA) failed (SocketTimeoutException) to wait for space of
> len=1190: waitForCondition(Window[server/remote](ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]))
> timeout exceeded: 20000
> 2019-10-24 12:34:06,129 DEBUG [org.apache.sshd.server.channel.ChannelSession]
> (Thread-44 (HornetQ-client-global-threads-407809182))
> flush(ChannelOutputStream[ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]]
> SSH_MSG_CHANNEL_DATA) failed (SocketTimeoutException) to wait for space of
> len=1190: waitForCondition(Window[server/remote](ChannelSession[id=0,
> recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58628]))
> timeout exceeded: 20000
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
