July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- Nope, still blocks: {noformat} java.lang.Thread.State: RUNNABLE [testng] at org.wildfly.openssl.SSLImpl.pendingWrittenBytesInBIO0(Native Method) [testng] at org.wildfly.openssl.SSLImpl.pendingWrittenBytesInBIO(SSLImpl.java:90) [testng] at org.wildfly.openssl.OpenSSLEngine.wrap(OpenSSLEngine.java:431) [testng] - locked <0x00000007cfbdcf18> (a org.wildfly.openssl.OpenSSLEngine) [testng] at javax.net.ssl.SSLEngine.wrap(java.base@11.0.1/SSLEngine.java:479) [testng] at org.wildfly.openssl.OpenSSLSocket.runHandshake(OpenSSLSocket.java:291) [testng] at org.wildfly.openssl.OpenSSLSocket.startHandshake(OpenSSLSocket.java:210) [testng] at org.jgroups.protocols.SSL_KEY_EXCHANGE.accept(SSL_KEY_EXCHANGE.java:257) [testng] at org.jgroups.protocols.SSL_KEY_EXCHANGE$$Lambda$315/0x00000008004a1c40.run(Unknown Source) [testng] at org.jgroups.util.Runner.run(Runner.java:75) [testng] at java.lang.Thread.run(java.base@11.0.1/Thread.java:834) {noformat} > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- OK, so I set this field to true by default, and the testsuite passed. I'll keep an eye on this for the next couple of runs. Should the testsuite continue to pass at a 100%, I'll leave it {{true}}. Closing this issue for now... > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5031) [GSS](7.3.z) remove the audit-log deprecation

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFCORE-5031?page=com.atlassian.jira.plug... ] Ranabir Chakraborty moved JBEAP-19821 to WFCORE-5031: ----------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5031 (was: JBEAP-19821) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Affects Version/s: (was: 7.3.2.GA) > [GSS](7.3.z) remove the audit-log deprecation > --------------------------------------------- > > Key: WFCORE-5031 > URL: https://issues.redhat.com/browse/WFCORE-5031 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Ranabir Chakraborty > Assignee: Ranabir Chakraborty > Priority: Minor > > Remove the audit-log deprecation as it was deprecated when planning to move the core-management=xxx resources into subsystems, but focus has since shifted from management to making our stuff work better in images. > *Deprecated* Since 1.7.0 > The management audit log configuration is deprecated and may be removed or moved in future versions. > [http://wildscribe.github.io/JBoss%20EAP/7.2/core-service/management/acces...] > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- OK, so I changed the logic a bit. I don't try to load the Wildfly lib(s) when {{use_native_if_available}} if false. When the test passes, I can simply change this field to {{true}} by default. > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13643) Test of WFLY-13592 "Jndi-view doen't show values for EJB in java:jboss/exported"

by Parul Sharma (Jira)

Parul Sharma created WFLY-13643: ----------------------------------- Summary: Test of WFLY-13592 "Jndi-view doen't show values for EJB in java:jboss/exported" Key: WFLY-13643 URL: https://issues.redhat.com/browse/WFLY-13643 Project: WildFly Issue Type: Bug Components: Naming Reporter: Parul Sharma Assignee: Parul Sharma -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13643) Test of WFLY-13592 "Jndi-view doen't show values for EJB in java:jboss/exported"

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13643?page=com.atlassian.jira.plugi... ] Parul Sharma updated WFLY-13643: -------------------------------- Description: Test Case of this issue https://issues.redhat.com/browse/WFLY-13592 jndi-view() show values as '?' for EJB on java:jboss/exported tree. > Test of WFLY-13592 "Jndi-view doen't show values for EJB in java:jboss/exported" > -------------------------------------------------------------------------------- > > Key: WFLY-13643 > URL: https://issues.redhat.com/browse/WFLY-13643 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > > Test Case of this issue https://issues.redhat.com/browse/WFLY-13592 > jndi-view() show values as '?' for EJB on java:jboss/exported tree. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5478) Propagate DataDictionary to avoid "Object" returned types

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5478: ---------------------------------------- Summary: Propagate DataDictionary to avoid "Object" returned types Key: DROOLS-5478 URL: https://issues.redhat.com/browse/DROOLS-5478 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi FieldRef and Apply functions does not define directly the returned type. Propagating DataDictionary will allow to avoid generic "Object" return and replace it with specific one -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- Actually, I added a field {{use_native_if_available}} to {{SSL_KEY_EXCHANGE}} (default: {{false}}), and pass it to {{SSLContextFactory}} when getting a context. > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2484: -------------------------------- If you run {{ant encrypt}}, the testsuite hangs. Without WF's openssl, it passes. I'm going to restructure this slightly, so that this is disabled by default, and enabled when setting {{org.jgroups.openssl}} to {{true}}, until this is fixed > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5477) Support instance of in the same way as Legacy Drools

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5477: ------------------------------------ Summary: Support instance of in the same way as Legacy Drools Key: DROOLS-5477 URL: https://issues.redhat.com/browse/DROOLS-5477 Project: Drools Issue Type: Bug Components: executable model Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020