September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13907) Upgrade to Bootable JAR 2.0.0.Beta8

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-13907: ------------------------------------------- Summary: Upgrade to Bootable JAR 2.0.0.Beta8 Key: WFLY-13907 URL: https://issues.redhat.com/browse/WFLY-13907 Project: WildFly Issue Type: Component Upgrade Components: Test Suite Reporter: Jean Francois Denise Assignee: Jean Francois Denise This plugin contains an upgrade of Galleon to 4.2.6.Final that fixes https://issues.redhat.com/browse/GAL-325. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12825) Artemis network health check feature not configurable from WildFly

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12825?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12825: ------------------------------------ Labels: (was: EAP-CD21 eap-7.3.0-deferred) > Artemis network health check feature not configurable from WildFly > ------------------------------------------------------------------ > > Key: WFLY-12825 > URL: https://issues.redhat.com/browse/WFLY-12825 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 18.0.1.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > To help mitigate the possibility of split brain problems Artemis has the ability to ping a configurable list of hosts to check the health of the brokers network connection, this feature is configured using the following parameters: > network-check-period > network-check-timeout > network-check-list > network-check-ping-command > network-check-ping6-command > None of these parameters are available from an EAP configuration. > https://activemq.apache.org/components/artemis/documentation/latest/netwo... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

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: -------------------------------------------------- [~jamezp] since we are already here, could you describe the steps. I sincerely thought replacing the modules and changing standalone.conf was enough. > 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)

5 years

1
0
0 / 0

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

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13906?page=com.atlassian.jira.plugi... ] Jean Francois Denise updated WFLY-13906: ---------------------------------------- Priority: Critical (was: Major) > 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 > Priority: Critical > > 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)

5 years

1
0
0 / 0

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

5 years

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)

5 years

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)

5 years

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)

5 years

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)

5 years

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)

5 years

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