February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1754) Update test for JDK cipher suites cover when TLS 1.3 support is added

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/ELY-1754?page=com.atlassian.jira.plugin.s... ] Diana Vilkolakova updated ELY-1754: ----------------------------------- Issue Type: Task (was: Bug) > Update test for JDK cipher suites cover when TLS 1.3 support is added > --------------------------------------------------------------------- > > Key: ELY-1754 > URL: https://issues.jboss.org/browse/ELY-1754 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Diana Vilkolakova > Priority: Major > > Elytron testsuite contains test whether Mechanism Database covers all cipher suites from JDK. Currently we are excluding testing for cipher suites from TLS 1.3. After the support of TLS 1.3 is added, this test should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1691) Add test if Mechansim Database cover cipher suites from JDK

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/ELY-1691?page=com.atlassian.jira.plugin.s... ] Diana Vilkolakova updated ELY-1691: ----------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1235, https://github.com/wildfly-security/wildfly-elytron/pull/1206 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1235) > Add test if Mechansim Database cover cipher suites from JDK > ----------------------------------------------------------- > > Key: ELY-1691 > URL: https://issues.jboss.org/browse/ELY-1691 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.7.0.CR2 > Reporter: Martin Choma > Assignee: Diana Vilkolakova > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1691) Add test if Mechansim Database cover cipher suites from JDK

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/ELY-1691?page=com.atlassian.jira.plugin.s... ] Diana Vilkolakova updated ELY-1691: ----------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1235 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1206) > Add test if Mechansim Database cover cipher suites from JDK > ----------------------------------------------------------- > > Key: ELY-1691 > URL: https://issues.jboss.org/browse/ELY-1691 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.7.0.CR2 > Reporter: Martin Choma > Assignee: Diana Vilkolakova > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4326) Follow up on WFCORE-3826 to add mechanism override support to the native connector.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4326: ---------------------------------------- Summary: Follow up on WFCORE-3826 to add mechanism override support to the native connector. Key: WFCORE-4326 URL: https://issues.jboss.org/browse/WFCORE-4326 Project: WildFly Core Issue Type: Bug Components: Remoting Affects Versions: 8.0.0.Beta5 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Beta6 The fix developed under WFCORE-3826 fixes the HTTP connector, this issue is to add the same fix to the native connector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1754) Update test for JDK cipher suites cover when TLS 1.3 support is added

by Diana Vilkolakova (Jira)

Diana Vilkolakova created ELY-1754: -------------------------------------- Summary: Update test for JDK cipher suites cover when TLS 1.3 support is added Key: ELY-1754 URL: https://issues.jboss.org/browse/ELY-1754 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Reporter: Diana Vilkolakova Elytron testsuite contains test whether Mechanism Database covers all cipher suites from JDK. Currently we are excluding testing for cipher suites from TLS 1.3. After the support of TLS 1.3 is added, this test should be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-218) JBoss Logmanager is incompatibile with -Xbootclasspath and JDK 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-218?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-218: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/216, https://github.com/jboss-logging/jboss-logmanager/pull/217, https://github.com/jboss-logging/jboss-logmanager/pull/218, https://github.com/jboss-logging/jboss-logmanager/pull/228, https://github.com/jboss-logging/jboss-logmanager/pull/229, https://github.com/jboss-logging/jboss-logmanager/pull/230 (was: https://github.com/jboss-logging/jboss-logmanager/pull/216, https://github.com/jboss-logging/jboss-logmanager/pull/217, https://github.com/jboss-logging/jboss-logmanager/pull/218) > JBoss Logmanager is incompatibile with -Xbootclasspath and JDK 11 > ----------------------------------------------------------------- > > Key: LOGMGR-218 > URL: https://issues.jboss.org/browse/LOGMGR-218 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Critical > Fix For: 2.1.6.Final, 2.1.7.Final, 2.2.0.Final, 3.0.0.Final > > > The current logmanager implementation is incompatible with use with the -Xbootclasspath/a option on JDK 11. The is because it is a multi-release jar which is incompatible with -Xbootclasspath/a. This is problematic because to allow Java Agents to work with JBoss Modules based applications (i.e. WildFly and derivatives) often it is necessary to include logmanager in -Xbootclasspath/a . > Here's me starting WildFly with a -Xbootclasspath/a setting and JDK 11: > {code} > $ build/target/wildfly-core-7.0.0.CR2-SNAPSHOT/bin/standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/bstansberry/dev/wildfly/wildfly-core/build/target/wildfly-core-7.0.0.CR2-SNAPSHOT > JAVA: /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djava.awt.headless=true -Xbootclasspath/a:/Users/bstansberry/dev/wildfly/wildfly-core/dist/target/wildfly-core-7.0.0.CR2-SNAPSHOT/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.1.5.Final.jar -Djava.util.logging.manager=org.jboss.logmanager.LogManager --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED --add-modules=java.se > ========================================================================= > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.jboss.logmanager.LogLevelInitTask to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level) > WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogLevelInitTask > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:57) > at org.jboss.as.server@7.0.0.CR2-SNAPSHOT//org.jboss.as.server.Main.main(Main.java:89) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > {code} > Right now jboss-logmanager is a multi-release jar. But, per the MR jar spec (https://openjdk.java.net/jeps/238) that is incompatible with -Xbootclasspath: > {quote} > Multi-release jars and the boot loader > Multi-release JARs are not supported by the boot loader (for example, when a multi-release JAR file is declared with the -Xbootclasspath/a option). Such support would complicate the boot loader implementation for what is considered a rare use-case. > {quote} > At this point I've identified two java agents that are commonly used with WildFly derived apps that cannot be installed in a JDK 11 environment: Hawkular and the Prometheus jmx-exporter. The former I could perhaps work around (i.e. don't install it with JDK 11) as it's use is deprecated. But being able to use of jmx-exporter is quite important. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-599) Build Openshift 3.11 Cluster On B15

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-599: ---------------------------------- Summary: Build Openshift 3.11 Cluster On B15 Key: SWSQE-599 URL: https://issues.jboss.org/browse/SWSQE-599 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11702) Upgrade Yasson to 1.0.3

by Patrick Reinhart (Jira)

[ https://issues.jboss.org/browse/WFLY-11702?page=com.atlassian.jira.plugin... ] Patrick Reinhart updated WFLY-11702: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12061 > Upgrade Yasson to 1.0.3 > ----------------------- > > Key: WFLY-11702 > URL: https://issues.jboss.org/browse/WFLY-11702 > Project: WildFly > Issue Type: Component Upgrade > Components: EE, REST > Affects Versions: 15.0.1.Final > Reporter: Patrick Reinhart > Assignee: Alessio Soldano > Priority: Critical > > Upgrade to Eclipse Yasson from 1.0.2 to 1.0.3 to fix JsonConfig taking custom JsonSerializers/JsonDeserializers into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11702) Upgrade Yasson to 1.0.3

by Patrick Reinhart (Jira)

Patrick Reinhart created WFLY-11702: --------------------------------------- Summary: Upgrade Yasson to 1.0.3 Key: WFLY-11702 URL: https://issues.jboss.org/browse/WFLY-11702 Project: WildFly Issue Type: Component Upgrade Components: EE, REST Affects Versions: 15.0.1.Final Reporter: Patrick Reinhart Assignee: Alessio Soldano Upgrade to Eclipse Yasson from 1.0.2 to 1.0.3 to fix JsonConfig taking custom JsonSerializers/JsonDeserializers into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11622) Multiple delivery group support for MDBs

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11622?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11622: --------------------------------------- [~flavia.rainone] [~kabirkhan] Pre-check is ok. Feature behaves as expected. I don't see any regressions in my tests. However there are some failures hit by CI jobs in PR: https://github.com/wildfly/wildfly/pull/12045 - is it normal those fail? > Multiple delivery group support for MDBs > ---------------------------------------- > > Key: WFLY-11622 > URL: https://issues.jboss.org/browse/WFLY-11622 > Project: WildFly > Issue Type: Feature Request > Components: EJB, JMS > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Add support for multiple delivery groups in the same MDB. > For info on delivery groups, see https://docs.jboss.org/author/display/WFLY10/Message+Driven+Beans+Control... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 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 February 2019