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

Gregory Hoffer commented on DIRMINA-1144:
-----------------------------------------

I am ready willing and eager to help (my focus and contributions are centered 
on SSH/SFTP).

NOTE that  Java 8 support ends much later than 2022: support ends in 2026 for 
OpenJDK and Amazon Corretto, and 2030 for Azul, both of which are *LATER* than 
the end of support for Java 11.

I am not recommending paying for extended support.  I am not even recommending 
paying for JRE usage. I am a huge proponent of OpenJDK based JDKs/JREs.  

I am simply recommending that, unless there are compelling reasons to abandon 
Java 8 as a target runtime environment.  Please at least consider the 
trade-offs between what you are gaining by requiring Java 9 or 11 vs. the loss 
of the most recent and complete branch running on Java 8, which would still be 
the most widely utilized JVM version in production.

I am only voicing one opinion, and concede to whatever choice is made.  But I 
am hoping to help make an informed choice, with the proper facts.

> Deadlock with SSL + Proxy
> -------------------------
>
>                 Key: DIRMINA-1144
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1144
>             Project: MINA
>          Issue Type: Bug
>          Components: SSL
>    Affects Versions: 2.1.3, 2.1.4
>            Reporter: Giuseppe Persico
>            Assignee: Jonathan Valliere
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: thread-dump-clean.txt
>
>
> You will find the thread dump attached. This seems to be a problem that 
> occurs using SSL in combination with proxy. I found the problem in the 2.1.4 
> and 2.1.3 versions. The 2.0.20, instead, seems to work,



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to