[jira] [Commented] (SSHD-1244) Client fails window adjust above Integer.MAX_VALUE

[ https://issues.apache.org/jira/browse/SSHD-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488555#comment-17488555 ] Ryosuke Kanda commented on SSHD-1244: - I'm sorry I'm late. I tried. Window Adjust was successful and

[jira] [Commented] (DIRMINA-1107) SslHandler flushScheduledEvents race condition, redux

[ https://issues.apache.org/jira/browse/DIRMINA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488507#comment-17488507 ] Emmanuel Lécharny commented on DIRMINA-1107: backported to 2.0 branch > SslHandler

[jira] [Updated] (DIRMINA-1107) SslHandler flushScheduledEvents race condition, redux

[ https://issues.apache.org/jira/browse/DIRMINA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny updated DIRMINA-1107: --- Fix Version/s: 2.0.23 > SslHandler flushScheduledEvents race condition, redux >

Re: Chage in NioDatagramAcceptor in 2.1 vs 2.0

Yeah, my point exactly, but wanted to be sure. Thanks Jonathan ! On 08/02/2022 01:15, Jonathan Valliere wrote: Actually, looks like I fixed something unrelated to DIRMINA-996 and marked it 996 for some reason. On Feb 7, 2022 at 5:43:49 PM, Emmanuel Lécharny wrote: The thing is that I

Re: Chage in NioDatagramAcceptor in 2.1 vs 2.0

Actually, looks like I fixed something unrelated to DIRMINA-996 and marked it 996 for some reason. On Feb 7, 2022 at 5:43:49 PM, Emmanuel Lécharny wrote: > The thing is that I can't see how it the commit is related to the > problem described in the JIRA... > > > On 07/02/2022 19:24, Jonathan

[jira] [Updated] (DIRMINA-1123) Receive buffer size is never set for NIO acceptor

[ https://issues.apache.org/jira/browse/DIRMINA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny updated DIRMINA-1123: --- Fix Version/s: 2.0.23 > Receive buffer size is never set for NIO acceptor >

[jira] [Reopened] (DIRMINA-1123) Receive buffer size is never set for NIO acceptor

[ https://issues.apache.org/jira/browse/DIRMINA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lécharny reopened DIRMINA-1123: Assignee: (was: Jonathan Valliere) Reopened to backport the fix to 2.0.X

Re: Chage in NioDatagramAcceptor in 2.1 vs 2.0

The thing is that I can't see how it the commit is related to the problem described in the JIRA... On 07/02/2022 19:24, Jonathan Valliere wrote: Mark fixed On Mon, Feb 7, 2022 at 12:14 PM Emmanuel Lécharny > wrote: Hi Jonathan, the commit

Re: Chage in NioDatagramAcceptor in 2.1 vs 2.0

Mark fixed On Mon, Feb 7, 2022 at 12:14 PM Emmanuel Lécharny wrote: > Hi Jonathan, > > the commit 896b170d8d7c0769bca171f0fbe7de9b13a65968 is commented as a > fix for DIRMINA-996 > ( > https://github.com/apache/mina/commit/896b170d8d7c0769bca171f0fbe7de9b13a65968 > ) > > Is it the case? > > If

Chage in NioDatagramAcceptor in 2.1 vs 2.0

Hi Jonathan, the commit 896b170d8d7c0769bca171f0fbe7de9b13a65968 is commented as a fix for DIRMINA-996 (https://github.com/apache/mina/commit/896b170d8d7c0769bca171f0fbe7de9b13a65968) Is it the case? If so, can we close the issue and mark it fixed (note: the patch has been applied to 2.1