September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13906) Upgrade to Galleon 4.2.6

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13906: ------------------------------------------- Summary: Upgrade to Galleon 4.2.6 Key: WFLY-13906 URL: https://issues.redhat.com/browse/WFLY-13906 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise The main change is a fix for the issue https://issues.redhat.com/browse/GAL-325. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5142) Upgrade to Galleon 4.2.6.Final

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-5142: -------------------------------------------- Summary: Upgrade to Galleon 4.2.6.Final Key: WFCORE-5142 URL: https://issues.redhat.com/browse/WFCORE-5142 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise Includes a fix for the issue https://issues.redhat.com/browse/GAL-325 that, although not required for wildfly-core, would be good to see fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5139) Upgrade Bootable JAR Maven plugin to 2.0.0.Beta8

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5139?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-5139: ----------------------------------------- Summary: Upgrade Bootable JAR Maven plugin to 2.0.0.Beta8 (was: Upgrade Bootable JAR Maven plugin to 2.0.0.Beta7) > Upgrade Bootable JAR Maven plugin to 2.0.0.Beta8 > ------------------------------------------------ > > Key: WFCORE-5139 > URL: https://issues.redhat.com/browse/WFCORE-5139 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13905) Support ProtoStream marshalling of @Stateful EJB instances

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13905: ----------------------------------- Summary: Support ProtoStream marshalling of @Stateful EJB instances Key: WFLY-13905 URL: https://issues.redhat.com/browse/WFLY-13905 Project: WildFly Issue Type: Sub-task Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro This encompasses the EJB instance itself, along with its attributes, including: * Serializable JDK classes * Application specific classes * References to other EJBs * Injected objects allowed by the spec, including: ** References to a UserTransaction ** References to a resource manager connection factory ** References to a container managed EntityManager or EntityManagerFactory ** References to an EJB Timer object The scope of this Jira does not include: * Marshalling of EJB method parameters and responses for use with @Remote invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13904) Support ProtoStream marshalling of web session attributes

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13904: ----------------------------------- Summary: Support ProtoStream marshalling of web session attributes Key: WFLY-13904 URL: https://issues.redhat.com/browse/WFLY-13904 Project: WildFly Issue Type: Sub-task Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro This encompasses any type of object that can be placed into an HttpSession, including: * Serializable JDK classes * JSF classes * Weld classes for handling session scope * EJB references * Application specific classes This will not include: * Non-serializable JDK classes * EJB instances (these will be handled separately) * 3rd party web framework classes ** Perhaps create wildlfy-extra repos for some of the more common frameworks -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13901) Upgrade Jastow from 2.0.8.Final to 2.0.9.Final

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFLY-13901?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFLY-13901: ---------------------------------- Description: https://github.com/undertow-io/jastow/compare/2.0.8.Final...2.0.9.Final > Upgrade Jastow from 2.0.8.Final to 2.0.9.Final > ---------------------------------------------- > > Key: WFLY-13901 > URL: https://issues.redhat.com/browse/WFLY-13901 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 21.0.0.Final > > > https://github.com/undertow-io/jastow/compare/2.0.8.Final...2.0.9.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13855) remote-cache-container protocol-version allowed values contain last protocol version twice

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13855?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13855: ---------------------------------- Summary: remote-cache-container protocol-version allowed values contain last protocol version twice (was: remote-cache-container protocol-version allowed values contains last protocol version twice) > remote-cache-container protocol-version allowed values contain last protocol version twice > ------------------------------------------------------------------------------------------ > > Key: WFLY-13855 > URL: https://issues.redhat.com/browse/WFLY-13855 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final, 20.0.1.Final, 21.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 21.0.0.Final > > > Clearly because of {{org.infinispan.client.hotrod.ProtocolVersion#PROTOCOL_VERSION_AUTO}} plus there is no pruning in place. > Fix is to use {{org.jboss.as.clustering.controller.validation.EnumValidator#EnumValidator(java.lang.Class<E>, java.util.EnumSet<E>)}} instead. > {code:json} > "protocol-version" => { > "type" => STRING, > "description" => "This property defines the protocol version that this client should use.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "3.0", > "allowed" => [ > "2.0", > "2.1", > "2.2", > "2.3", > "2.4", > "2.5", > "2.6", > "2.7", > "2.8", > "2.9", > "3.0", > "3.0" > ], > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13855) remote-cache-container protocol-version allowed values contains last protocol version twice

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13855?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13855: ---------------------------------- Affects Version/s: 21.0.0.Beta1 > remote-cache-container protocol-version allowed values contains last protocol version twice > ------------------------------------------------------------------------------------------- > > Key: WFLY-13855 > URL: https://issues.redhat.com/browse/WFLY-13855 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final, 20.0.1.Final, 21.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 21.0.0.Final > > > Clearly because of {{org.infinispan.client.hotrod.ProtocolVersion#PROTOCOL_VERSION_AUTO}} plus there is no pruning in place. > Fix is to use {{org.jboss.as.clustering.controller.validation.EnumValidator#EnumValidator(java.lang.Class<E>, java.util.EnumSet<E>)}} instead. > {code:json} > "protocol-version" => { > "type" => STRING, > "description" => "This property defines the protocol version that this client should use.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "3.0", > "allowed" => [ > "2.0", > "2.1", > "2.2", > "2.3", > "2.4", > "2.5", > "2.6", > "2.7", > "2.8", > "2.9", > "3.0", > "3.0" > ], > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ] Jean Francois Denise commented on WFLY-13903: --------------------------------------------- [~brian.stansberry], yes the mentioned failure related to galleon is: https://issues.redhat.com/browse/WFLY-13898 > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFLY-13903 > URL: https://issues.redhat.com/browse/WFLY-13903 > Project: WildFly > Issue Type: Task > Affects Versions: 21.0.0.Beta1 > Reporter: Fabio Burzigotti > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1]. > The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *Steps to reproduce*: > 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support > 2. build RESTEasy: > {code} > $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *fail* > 5. run the test against WF 20.0.1.Final with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

by Francisco De Melo Junior (Jira)

[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ] Francisco De Melo Junior commented on WFCORE-4674: -------------------------------------------------- Yes [~indrajit29], just changing the `standalone.conf` is +not**+ enough to solve the issue. This RFE changed the core module as he mentioned. I added this in the case. > Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4674 > URL: https://issues.redhat.com/browse/WFCORE-4674 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > Fix For: 13.0.0.Beta1 > > > If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path. > Example exception: > {code} > Failed to read or configure the org.jboss.logmanager.LogManager > java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON" > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65) > at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30) > at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172) > at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631) > at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701) > at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132) > at java.util.logging.LogManager$3.run(LogManager.java:399) > at java.util.logging.LogManager$3.run(LogManager.java:396) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) > at java.util.logging.LogManager.access$800(LogManager.java:145) > at java.util.logging.LogManager$2.run(LogManager.java:345) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) > at java.util.logging.LogManager.getLogManager(LogManager.java:378) > at org.jboss.modules.Main.main(Main.java:523) > Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader > at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556) > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63) > ... 19 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020