[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-07 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969400#comment-16969400
 ] 

Lyor Goldstein commented on SSHD-952:
-

Thx, I'll try and think about this issue some more - meanwhile, if you can 
somehow reproduce the behavior where the channel is not closed and provide some 
debugging information it would help a lot.

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-07 Thread Anudeep (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969075#comment-16969075
 ] 

Anudeep commented on SSHD-952:
--

Hi [~lgoldstein],

We tried in a different manner this time ,instead of blocking the read 
completely we added sleep while reading the data from channel on the client 
side .

This time even after the timeout it was still continuing for some time and got 
exited(channel got closed with an exception after some time). I suppose this 
behavior might be due to sleep which we introduced at client side.
{code:java}
 
pStatus=0.%A
2019-11-07 05:42:33,149 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] 
(sshd-SshServer[57e76ebb](port=8345)-nio2-thread-2) 
exceptionCaught(Nio2Session[local=/10.247
.246.52:8345, remote=/192.168.0.42:49984]) caught 
InterruptedByTimeoutException[null] - calling handler
2019-11-07 05:42:33,149 WARN  
[org.apache.sshd.server.session.ServerSessionImpl] 
(sshd-SshServer[57e76ebb](port=8345)-nio2-thread-2) 
exceptionCaught(ServerSessionImpl[a
dministrator@/192.168.0.42:49984])[state=Opened] InterruptedByTimeoutException: 
null
2019-11-07 05:42:33,150 DEBUG 
[org.apache.sshd.server.session.ServerSessionImpl] 
(sshd-SshServer[57e76ebb](port=8345)-nio2-thread-2) 
exceptionCaught(ServerSessionImpl[a
dministrator@/192.168.0.42:49984])[state=Opened] details: 
java.nio.channels.InterruptedByTimeoutException
at 
sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
 [rt.jar:1.8.0_221]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[rt.jar:1.8.0_221]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[rt.jar:1.8.0_221]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [rt.jar:1.8.0_221]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [rt.jar:1.8.0_221]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[rt.jar:1.8.0_221]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[rt.jar:1.8.0_221]
:

{code}


Thanks,
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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-06 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968681#comment-16968681
 ] 

Lyor Goldstein commented on SSHD-952:
-

{quote}
we blocked client to read data to make the window full 
{quote}
How did you do that ?

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-06 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968680#comment-16968680
 ] 

Lyor Goldstein commented on SSHD-952:
-

Initial scanning of the code seems to indicate that if there is a timeout 
exception then the channel is closed (maybe not the session). I cannot find any 
trace of the behavior you mention especially
{quote}
spawning a new thread
{quote}
can you make sure that it isn't your code that is somehow spanning the thread ? 
I will still try and think of scenario that might explain what you describe, 
but off-hand I do not have a lead yet as to a promising avenue of 
investigation. Alternatively, can you perhaps debug the scenario where the 
timeout occurs and try to figure out what is going on - since you seem to be 
able to reproduce it. Perhaps it will yield more useful information.

 

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-05 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967723#comment-16967723
 ] 

Lyor Goldstein commented on SSHD-952:
-

I'll try and look into it - may take a while (I am fairly swamped). Meanwhile, 
if you wish you can analyze the code and perhaps submit a pull-request - we 
welcome contributions...

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-11-05 Thread Anudeep (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967487#comment-16967487
 ] 

Anudeep commented on SSHD-952:
--

In our test we blocked client to read data to make the window full and then we 
observed it was timing out and then spawning a new thread.Client session was 
not closed.

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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-10-31 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964185#comment-16964185
 ] 

Lyor Goldstein commented on SSHD-952:
-

{quote}
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?
{quote}
As far as I can tell it will close the session due to the thrown exception

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-10-31 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964179#comment-16964179
 ] 

Lyor Goldstein commented on SSHD-952:
-

{quote}
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.
{quote}
I am inclined to agree - examining the GIT log indicates such a change in order 
to address SSHD-565

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-10-30 Thread Anudeep (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962756#comment-16962756
 ] 

Anudeep commented on SSHD-952:
--

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 ?

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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-10-29 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962231#comment-16962231
 ] 

Lyor Goldstein commented on SSHD-952:
-

{quote}
on timeout thread get released and it spawns a new thread on timeout
{quote}
I think it only +seems+ that way - reminder: the code is using +asynchronous 
NIO+ calls along with a thread pool. I think what happens here is that after 
one thread times out, another thread takes its place and waits for space to 
become available. IMO, the more interesting question to ask is +why+ is there a 
timeout on waiting for channel data space.

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org



[jira] [Commented] (SSHD-952) What is the expected behavior of waitForSpace(long millis) method on default timeout of 30 seconds

2019-10-29 Thread Lyor Goldstein (Jira)


[ 
https://issues.apache.org/jira/browse/SSHD-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962225#comment-16962225
 ] 

Lyor Goldstein commented on SSHD-952:
-

{quote}
the expected behavior of waitForSpace(long millis) method of Window.java class
{quote}
See the Javadoc:
{quote}
Waits until some data becomes available or timeout expires
{quote}
Quick reminder: according to [RFC-4254 - section 
5|https://tools.ietf.org/html/rfc4254#section-5]
{quote}
Channels are flow-controlled.  No data may be sent to a channel until
 a message is received to indicate that window space is available.
{quote}
This code simply implements that logic

> 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: 2
> 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: 2
> 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: 2



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org