March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Component/s: Security > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase fails only on IBM JDK, due to the following root cause: > {code} > Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available > {code} > which in turn is due to the fact that the used algorithm is not available on IMB JDK, see for instance https://www-01.ibm.com/support/docview.wss?uid=swg1IT04505 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Steps to Reproduce: {code} $ cd testsuite/integration/web $ mvn clean install -Delytron -Dtest=*WebSecurityCERTTestCase {code} was: $ cd testsuite/integration/web $ mvn clean install -Delytron -Dtest=*WebSecurityCERTTestCase > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase fails only on IBM JDK, due to the following root cause: > {code} > Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available > {code} > which in turn is due to the fact that the used algorithm is not available on IMB JDK, see for instance https://www-01.ibm.com/support/docview.wss?uid=swg1IT04505 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti reassigned WFLY-13249: --------------------------------------- Assignee: (was: Fabio Burzigotti) > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase should be skipped when the Test Suite is executed against a server with enabled *elytron* subsystem, otherwise it would fail as it is supposed to run only against legacy security server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Description: The WebSecurityCERTTestCase fails only on IBM JDK, due to the following root cause: {code} Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available {code} which in turn is due to the fact that the used algorithm is not available on IMB JDK, see for instance https://www-01.ibm.com/support/docview.wss?uid=swg1IT04505 was:The WebSecurityCERTTestCase should be skipped when the Test Suite is executed against a server with enabled *elytron* subsystem, otherwise it would fail as it is supposed to run only against legacy security server. > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase fails only on IBM JDK, due to the following root cause: > {code} > Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available > {code} > which in turn is due to the fact that the used algorithm is not available on IMB JDK, see for instance https://www-01.ibm.com/support/docview.wss?uid=swg1IT04505 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Steps to Reproduce: $ cd testsuite/integration/web $ mvn clean install -Delytron -Dtest=*WebSecurityCERTTestCase > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase fails only on IBM JDK, due to the following root cause: > {code} > Caused by: java.security.NoSuchAlgorithmException: SunX509 TrustManagerFactory not available > {code} > which in turn is due to the fact that the used algorithm is not available on IMB JDK, see for instance https://www-01.ibm.com/support/docview.wss?uid=swg1IT04505 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Summary: WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled (was: Skipping WebSecurityCERTTestCase when elytron subsystem is enabled) > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Fabio Burzigotti > Assignee: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase should be skipped when the Test Suite is executed against a server with enabled *elytron* subsystem, otherwise it would fail as it is supposed to run only against legacy security server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13249) WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13249?page=com.atlassian.jira.plugi... ] Fabio Burzigotti updated WFLY-13249: ------------------------------------ Issue Type: Bug (was: Enhancement) > WebSecurityCERTTestCase fails on IBM JDK when elytron is enabled > ---------------------------------------------------------------- > > Key: WFLY-13249 > URL: https://issues.redhat.com/browse/WFLY-13249 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Fabio Burzigotti > Assignee: Fabio Burzigotti > Priority: Major > > The WebSecurityCERTTestCase should be skipped when the Test Suite is executed against a server with enabled *elytron* subsystem, otherwise it would fail as it is supposed to run only against legacy security server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-266) log4j2-jboss-logmanager LevelTranslator NullPointer

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/LOGMGR-266?page=com.atlassian.jira.plugi... ] Boris Unckel edited comment on LOGMGR-266 at 3/17/20 8:40 AM: -------------------------------------------------------------- There might be a second point: org.jboss.logmanager.log4j.JBossLogger {code:java} @Override public Level getLevel() { final java.util.logging.Level julLevel = logger.getLevel(); // Fallback to EffectiveLevel if underlying java.util.logging.Logger's level is null int julLevelEffectiveInt; if(julLevel == null) { julLevelEffectiveInt = logger.getEffectiveLevel(); } else { julLevelEffectiveInt = julLevel.intValue(); } return levelTranslator.translateLevel(julLevelEffectiveInt); } {code} and the translation by int in org.jboss.logmanager.log4j.LevelTranslator {code:java} Level translateLevel(final int julLevelInt) { final Level result = julToLog4j.get(julLevelInt); return result == null ? Level.INFO : result; } {code} was (Author: a13397): There might be a second point: org.jboss.logmanager.log4j.JBossLogger {source} @Override public Level getLevel() { final java.util.logging.Level julLevel = logger.getLevel(); // Fallback to EffectiveLevel if underlying java.util.logging.Logger's level is null int julLevelEffectiveInt; if(julLevel == null) { julLevelEffectiveInt = logger.getEffectiveLevel(); } else { julLevelEffectiveInt = julLevel.intValue(); } return levelTranslator.translateLevel(julLevelEffectiveInt); } {source} and the translation by int in org.jboss.logmanager.log4j.LevelTranslator {source} Level translateLevel(final int julLevelInt) { final Level result = julToLog4j.get(julLevelInt); return result == null ? Level.INFO : result; } {source} > log4j2-jboss-logmanager LevelTranslator NullPointer > --------------------------------------------------- > > Key: LOGMGR-266 > URL: https://issues.redhat.com/browse/LOGMGR-266 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: Boris Unckel > Priority: Critical > > We found the following Nullpointer Exception > {code} > Caused by: java.lang.NullPointerException > at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95) > at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156) > {code} > .... > Reason seems that LevelTranslator is not defensive enough. Suggestion: > {code} > java.util.logging.Level translateLevel(final Level level) { > //level null is same as level not translated > if(level == null) { > return org.jboss.logmanager.Level.INFO; > } > final java.util.logging.Level result = log4jToJul.get(level.intLevel()); > return result == null ? org.jboss.logmanager.Level.INFO : result; > } > Level translateLevel(final java.util.logging.Level level) { > //level null is same as level not translated > if(level == null) { > return Level.INFO; > } > final Level result = julToLog4j.get(level.intValue()); > return result == null ? Level.INFO : result; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-266) log4j2-jboss-logmanager LevelTranslator NullPointer

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/LOGMGR-266?page=com.atlassian.jira.plugi... ] Boris Unckel commented on LOGMGR-266: ------------------------------------- There might be a second point: org.jboss.logmanager.log4j.JBossLogger {source} @Override public Level getLevel() { final java.util.logging.Level julLevel = logger.getLevel(); // Fallback to EffectiveLevel if underlying java.util.logging.Logger's level is null int julLevelEffectiveInt; if(julLevel == null) { julLevelEffectiveInt = logger.getEffectiveLevel(); } else { julLevelEffectiveInt = julLevel.intValue(); } return levelTranslator.translateLevel(julLevelEffectiveInt); } {source} and the translation by int in org.jboss.logmanager.log4j.LevelTranslator {source} Level translateLevel(final int julLevelInt) { final Level result = julToLog4j.get(julLevelInt); return result == null ? Level.INFO : result; } {source} > log4j2-jboss-logmanager LevelTranslator NullPointer > --------------------------------------------------- > > Key: LOGMGR-266 > URL: https://issues.redhat.com/browse/LOGMGR-266 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: Boris Unckel > Priority: Critical > > We found the following Nullpointer Exception > {code} > Caused by: java.lang.NullPointerException > at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95) > at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156) > {code} > .... > Reason seems that LevelTranslator is not defensive enough. Suggestion: > {code} > java.util.logging.Level translateLevel(final Level level) { > //level null is same as level not translated > if(level == null) { > return org.jboss.logmanager.Level.INFO; > } > final java.util.logging.Level result = log4jToJul.get(level.intLevel()); > return result == null ? org.jboss.logmanager.Level.INFO : result; > } > Level translateLevel(final java.util.logging.Level level) { > //level null is same as level not translated > if(level == null) { > return Level.INFO; > } > final Level result = julToLog4j.get(level.intValue()); > return result == null ? Level.INFO : result; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5171) Investigate dashbuilder dependencies of scenariossimulation-kogito-runitme

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5171: ----------------------------------- Summary: Investigate dashbuilder dependencies of scenariossimulation-kogito-runitme Key: DROOLS-5171 URL: https://issues.redhat.com/browse/DROOLS-5171 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Jozef Marko Assignee: Jozef Marko There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. Investigate if they can not be removed. [1] {code:xml}  <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-widgets</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-validations</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-navigation-client</artifactId> <scope>provided</scope> <exclusions> <exclusion> <groupId>org.uberfire</groupId> <artifactId>uberfire-layout-editor-backend</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-renderer-default</artifactId> <scope>provided</scope> </dependency> {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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