It is going to be complicated to re-bind; probably the first patch will
simply let it fully fail. I’ll have to test the ulimit protection to see
if I can determine if the exception is related to ulimit or something else.
On Mon, Feb 26, 2018 at 11:35 AM, dgriff wrote:
Well according to this:
https://www.ibm.com/support/knowledgecenter/en/SSYKE2_9.0.0/com.ibm.java.multiplatform.90.doc/user/cinet.html
"an exception (NetworkRecycledException) is thrown to the application to
allow it either to fail or to attempt to rebind."
So is it possible to modify this code
Le 26/02/2018 à 17:06, Jonathan Valliere a écrit :
> Just a thought…
>
> At work, we always have a release target similar to 2.0-NEXT which always
> represents the next release. When a new release is completed, the target
> is renamed to the correct version number and a new 2.0-NEXT release is
[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Valliere updated DIRMINA-1076:
---
Component/s: Core
> Leaking NioProcessors/NioSocketConnectors hanging in call to
[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Valliere updated DIRMINA-1076:
---
Fix Version/s: 2.0.17
> Leaking NioProcessors/NioSocketConnectors hanging in call
[
https://issues.apache.org/jira/browse/DIRMINA-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Valliere updated DIRMINA-1077:
---
Fix Version/s: 2.0.17
> Threads hanging in dispose() on SSLHandshakeException
>
Just a thought…
At work, we always have a release target similar to 2.0-NEXT which always
represents the next release. When a new release is completed, the target
is renamed to the correct version number and a new 2.0-NEXT release is
created. This style makes it easier to configure and schedule
[
https://issues.apache.org/jira/browse/DIRMINA-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on DIRMINA-1077 started by Jonathan Valliere.
--
> Threads hanging in dispose() on SSLHandshakeException
>
[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on DIRMINA-1076 started by Jonathan Valliere.
--
> Leaking NioProcessors/NioSocketConnectors hanging in call to
[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376929#comment-16376929
]
Emmanuel Lecharny commented on DIRMINA-1076:
Sounds good !
Jonathan, let's wait for
[
https://issues.apache.org/jira/browse/DIRMINA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376881#comment-16376881
]
Christoph John commented on DIRMINA-1076:
-
Hi [~johnnyv], thanks for the patch. First tests
[
https://issues.apache.org/jira/browse/SSHD-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376628#comment-16376628
]
Goldstein Lyor edited comment on SSHD-792 at 2/26/18 10:34 AM:
---
See [SSH port
[
https://issues.apache.org/jira/browse/SSHD-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376628#comment-16376628
]
Goldstein Lyor commented on SSHD-792:
-
See [SSH port forwarding
13 matches
Mail list logo