January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14259) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14259: ------------------------------- Affects Version/s: 20.0.1.Final 20.0.0.Final > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFLY-14259 > URL: https://issues.redhat.com/browse/WFLY-14259 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14259) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi... ] Jeff Mesnil edited comment on WFLY-14259 at 1/4/21 10:37 AM: ------------------------------------------------------------- [~d.lepczynski] thanks for the report, do you have a reproducer test we can use to verify the issue? Are you still facing the issue with the latest WildFly release (21.0.2.Final)? was (Author: jmesnil): [~d.lepczynski] thanks for the report, do you have a reproducer test we can use to verify the issue? > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFLY-14259 > URL: https://issues.redhat.com/browse/WFLY-14259 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14259) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi... ] Jeff Mesnil moved WFCORE-5235 to WFLY-14259: -------------------------------------------- Key: WFLY-14259 (was: WFCORE-5235) Project: WildFly (was: WildFly Core) > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFLY-14259 > URL: https://issues.redhat.com/browse/WFLY-14259 > Project: WildFly > Issue Type: Bug > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14259) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-14259: ------------------------------------ [~fjuma] When we have a reproducer, could you please have a look? > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFLY-14259 > URL: https://issues.redhat.com/browse/WFLY-14259 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14259) URL.openStream fails handshake on WildFly

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-14259?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-14259: ------------------------------------ Component/s: Security > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFLY-14259 > URL: https://issues.redhat.com/browse/WFLY-14259 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5235) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5235?page=com.atlassian.jira.plug... ] Jeff Mesnil commented on WFCORE-5235: ------------------------------------- [~d.lepczynski] thanks for the report, do you have a reproducer test we can use to verify the issue? > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFCORE-5235 > URL: https://issues.redhat.com/browse/WFCORE-5235 > Project: WildFly Core > Issue Type: Bug > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5235) URL.openStream fails handshake on WildFly

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5235?page=com.atlassian.jira.plug... ] Jeff Mesnil reassigned WFCORE-5235: ----------------------------------- Assignee: (was: Jeff Mesnil) > URL.openStream fails handshake on WildFly > ----------------------------------------- > > Key: WFCORE-5235 > URL: https://issues.redhat.com/browse/WFCORE-5235 > Project: WildFly Core > Issue Type: Bug > Reporter: Dominik Lepczyński > Priority: Major > > There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. > Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5235) URL.openStream fails handshake on WildFly

by Dominik Lepczyński (Jira)

Dominik Lepczyński created WFCORE-5235: ------------------------------------------ Summary: URL.openStream fails handshake on WildFly Key: WFCORE-5235 URL: https://issues.redhat.com/browse/WFCORE-5235 Project: WildFly Core Issue Type: Bug Reporter: Dominik Lepczyński Assignee: Jeff Mesnil There's a problem connecting using TLS v1.3 using JSSE (URL.openStream). Connection works on the same JDK and machine in a standalone Java program. Only when the code is executed on WildFly the server_name extension is going AWOL from ClientHello message, and the connection fails with handshake_failure. It seems to be a bug in WildFly, because it happens only when running on WildFly with the rest of the code identical. Tested on WildFly 20.0.0.Final and 20.0.1.Final using AdoptOpenJDK 11.0.9.1_1. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1171) Create automated cleaning of old OCP clusters

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1171?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1171: ---------------------------------- Sprint: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51 (was: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50) > Create automated cleaning of old OCP clusters > --------------------------------------------- > > Key: SWSQE-1171 > URL: https://issues.redhat.com/browse/SWSQE-1171 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Leonardo Ieggli > Priority: Major > Labels: infrastructure > > We need some cleaning mechanism for old OCP clusters. Probably to have some list of long living clusters and remove all other clusters after e.g. 1 week. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1248) Kiali soak test

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1248?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1248: ---------------------------------- Sprint: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50, Kiali Sprint #51 (was: Kiali Sprint #48, Kiali Sprint #49, Kiali Sprint #50) > Kiali soak test > --------------- > > Key: SWSQE-1248 > URL: https://issues.redhat.com/browse/SWSQE-1248 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need some long running instance of SM -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021