July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2478) Fibers: test performance versus regular threads

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2478?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2478: --------------------------- Fix Version/s: 5.0.0.Final (was: 5.1) I made all dependencies on fibers and JDK 16 stuff dependent on the presence of fibers (using {{MethodHandle}}), so this stuff can still go into 5 final as it compiles and doesn't hamper 5. > Fibers: test performance versus regular threads > ----------------------------------------------- > > Key: JGRP-2478 > URL: https://issues.redhat.com/browse/JGRP-2478 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. > This requires a few code changes: > * There's no need to pool fibers, see [1] for details > * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} > * In a future version, we could simply remove the 2 thread pools > [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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: -------------------------------- ASYM_ENCRYPT_TestKeyExchange (and subclass) > 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)

6 years

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Tristan Tarrant commented on JGRP-2484: --------------------------------------- Yes it seems random. Which test was this ? > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5028) CallbackHandler from CLI overriding discovered wildfly-config for authentication.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5028?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-5028: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4252, https://github.com/wildfly/wildfly-core/pull/4253 (was: https://github.com/wildfly/wildfly-core/pull/4252) > CallbackHandler from CLI overriding discovered wildfly-config for authentication. > --------------------------------------------------------------------------------- > > Key: WFCORE-5028 > URL: https://issues.redhat.com/browse/WFCORE-5028 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 12.0.2.Final, 13.0.0.Beta2 > > > WFCORE-4976 made an update to ProtocolConnectionUtils so that a supplied CallbackHandler takes priority - this works where a client is using ModelControllerClient.create() and passing in a CallbackHandler as we should take that as an indication that the caller wants control of authentication. > However by fixing in ProtocolConnectionUtils it has also picked up the case where the CLI passes in the CallbackHandler - that case however should only use the CBH if the information can not be obtained from the AuthenticationConfiguration. This call does not come via ModelControllerClient but both paths meet at ProtocolConnectionUtils. > Either the adjustment of the AuthenticationContext to give the CallbackHandler should happen in ModelControllerClient - or an additional boolean should be passed into ProtocolConnectionUtils to indicate if the CallbackHandler should be given priority. The latter may be a less invasive evolution of the fix prepared so far. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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: -------------------------------- 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)

6 years

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)

6 years

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)

6 years

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)

6 years

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)

6 years

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)

6 years

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 July 2020