[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358278#comment-17358278 ] Christoph John edited comment on DIRMINA-1144 at 6/6/21, 11:12 PM: --- Hi [~elecharny] / [~johnnyv] this looks the same as DIRMINA-1119. I don't know why but both issues appear when using QuickFIX/J (https://github.com/quickfix-j/quickfixj/). But I am not aware of doing anything special that would cause this. However, do you know why this does not appear with MINA 2.0.20? I thought the only difference was the part about the notifications outlined here: https://mina.apache.org/mina-project/2.1-vs-2.0.html Thanks in advance, Chris. was (Author: chrjohn): Hi [~elecharny] / [~johnnyv] this looks the same as DIRMINA-1119. I don't know why but both issues appear when using QuickFIX/J. But I am not aware of doing anything special that would cause this. However, do you know why this does not appear with MINA 2.0.20? I thought the only difference was the part about the notifications outlined here: https://mina.apache.org/mina-project/2.1-vs-2.0.html Thanks in advance, Chris. > 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 >Priority: Critical > Fix For: 2.0.20 > > 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.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404451#comment-17404451 ] Christoph John edited comment on DIRMINA-1144 at 8/25/21, 1:43 PM: --- [~johnnyv] just a question. Is there a SNAPSHOT build around somewhere for that branch? Would make it easier to create a QFJ branch if the dependency could be automatically downloaded. Thanks. was (Author: chrjohn): [~johnnyv] just a question. Is there a SNAPSHOT build on Central for that branch? Would make it easier to create a QFJ branch if the dependency could be automatically downloaded. Thanks. > 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.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443221#comment-17443221 ] Christoph John edited comment on DIRMINA-1144 at 11/13/21, 11:43 PM: - [~sebb] [~johnnyv] for https://github.com/quickfix-j/quickfixj/pull/440 I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. was (Author: chrjohn): [~sebb] [~johnnyv] I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[
https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443247#comment-17443247
]
Emmanuel Lécharny edited comment on DIRMINA-1144 at 11/14/21, 7:26 AM:
---
Snapshots are not necessarily generated. In order to have a 2.2.0-SNAPSHOT
available, one has to do a {{mvn deploy}}.
was (Author: elecharny):
Snapshots are not necessarily generated. In order to have a 2.2.0-SNAPSHOT
available, one has to do a ```mvn deploy```.
> 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: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443221#comment-17443221 ] Christoph John edited comment on DIRMINA-1144 at 11/14/21, 11:47 PM: - [~sebb] [~johnnyv] for https://github.com/quickfix-j/quickfixj/pull/441 I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. was (Author: chrjohn): [~sebb] [~johnnyv] for https://github.com/quickfix-j/quickfixj/pull/440 I tried to access the 2.2.0-SNAPSHOT from the Apache Repo but it cannot be found: https://repository.apache.org/content/groups/snapshots/org/apache/mina/mina-core/ Seems like 2.2.0-SNAPSHOT is missing there, but other snapshots are there. Am I missing something? Thanks, Chris. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443831#comment-17443831 ] Christoph John edited comment on DIRMINA-1144 at 11/15/21, 1:56 PM: [~johnnyv] thanks so far. I fixed the compile errors in my PR https://github.com/quickfix-j/quickfixj/pull/441 . 1. Could you please tell me how I can get a reference to the SSLSession? Formerly we were doing it via sslFilter.getSslSession(ioSession). 2. I noticed that we were relying on the autoStart flag for using a proxy (autoStart was disabled for using a prox). Is this not needed anymore? Thanks, Chris. was (Author: chrjohn): [~johnnyv] thanks so far. I fixed the compile errors in my PR https://github.com/quickfix-j/quickfixj/pull/441 . Can you tell me how I can get a reference to the SSLSession? Formerly we were doing it via sslFilter.getSslSession(ioSession). I noticed that we were relying on the autoStart flag for using a proxy (autoStart was disabled for using a prox). Is this not needed anymore? Thanks, Chris. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445126#comment-17445126 ] Christoph John edited comment on DIRMINA-1144 at 11/17/21, 12:13 PM: - OK, should I open a PR for the "--release" option? This problem could also happen on normal release builds, right? But up to now I didn't have this problem. was (Author: chrjohn): OK, should I open a PR for the "--release" option? > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[
https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445145#comment-17445145
]
Jonathan Valliere edited comment on DIRMINA-1144 at 11/17/21, 1:04 PM:
---
There is also another feature somewhere which requires Java 9 but I don't
remember what. Officially deprecating Java 8 is a good idea since it's not
really being maintained anymore. I'm also fairly sure there is some lambda
code somewhere which is also incompatible with Java 8.
P.S. [~chrjohn] 's error is with {{ByteBufer}}
{code:java}
java.lang.NoSuchMethodError: java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer;
{code}
{{ }}
was (Author: johnnyv):
There is also another feature somewhere which requires Java 9 but I don't
remember what. Officially deprecating Java 8 is a good idea since it's not
really being maintained anymore. I'm also fairly sure there is some lambda
code somewhere which is also incompatible with Java 8.
> 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: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445305#comment-17445305 ] Gregory Hoffer edited comment on DIRMINA-1144 at 11/17/21, 8:53 PM: respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 ([[https://adoptopenjdk.net/support.html||https://adoptopenjdk.net/support.html,] [https://adoptopenjdk.net/support.html|https://adoptopenjdk.net/support.html,] [], [https://www.azul.com/products/azul-support-roadmap/|https://adoptopenjdk.net/support.html,]|[https://www.azul.com/products/azul-support-roadmap/]|https://adoptopenjdk.net/support.html,], [[https://aws.amazon.com/corretto/faqs/||https://aws.amazon.com/corretto/faqs/] [https://aws.amazon.com/corretto/faqs/]], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. was (Author: JIRAUSER280397): respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 ([https://adoptopenjdk.net/support.html, https://www.azul.com/products/azul-support-roadmap/|https://adoptopenjdk.net/support.html,], [https://aws.amazon.com/corretto/faqs/], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445305#comment-17445305 ] Gregory Hoffer edited comment on DIRMINA-1144 at 11/17/21, 8:55 PM: respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 (c.f. [Adopt OpenJDK|https://adoptopenjdk.net/support.html], [Azul Zulu|[https://www.azul.com/products/azul-support-roadmap|https://adoptopenjdk.net/support.html,]], [Amazon Corretto|https://aws.amazon.com/corretto/faqs/], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. was (Author: JIRAUSER280397): respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 ([[https://adoptopenjdk.net/support.html||https://adoptopenjdk.net/support.html,] [https://adoptopenjdk.net/support.html|https://adoptopenjdk.net/support.html,] [], [https://www.azul.com/products/azul-support-roadmap/|https://adoptopenjdk.net/support.html,]|[https://www.azul.com/products/azul-support-roadmap/]|https://adoptopenjdk.net/support.html,], [[https://aws.amazon.com/corretto/faqs/||https://aws.amazon.com/corretto/faqs/] [https://aws.amazon.com/corretto/faqs/]], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Comment Edited] (DIRMINA-1144) Deadlock with SSL + Proxy
[ https://issues.apache.org/jira/browse/DIRMINA-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445305#comment-17445305 ] Gregory Hoffer edited comment on DIRMINA-1144 at 11/17/21, 8:56 PM: respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 (c.f. [Adopt OpenJDK|https://adoptopenjdk.net/support.html], [Azul Zulu|https://www.azul.com/products/azul-support-roadmap], [Amazon Corretto|https://aws.amazon.com/corretto/faqs/], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. was (Author: JIRAUSER280397): respectfully, Java 8 has the longest support life of any JDK out there right now – supported through at least 2026 (c.f. [Adopt OpenJDK|https://adoptopenjdk.net/support.html], [Azul Zulu|[https://www.azul.com/products/azul-support-roadmap|https://adoptopenjdk.net/support.html,]], [Amazon Corretto|https://aws.amazon.com/corretto/faqs/], et. al.). It is simply not accurate that Java 1.8 is not being maintained anymore. Java 11 LTS is shorter than Java 8 in many cases, which means that Java 8 is "guaranteed" to be supported for a long period of time than even the Java 11 LTS (weird, but true). I would encourage reconsidering changes that break on Java 8. I work with many customers who still use Java 8 because of its LTS, and are hesitant to move until they see what LTS will officially be for Java 17. > 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: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
