September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4675) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4675?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4675: ---------------------------------- Labels: OpenShift jdk11 (was: OpenShift jsk11) > Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final > ---------------------------------------------------------- > > Key: WFCORE-4675 > URL: https://issues.jboss.org/browse/WFCORE-4675 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.14.Final to 2.1.15.Final. > This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4676) Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final

by James Perkins (Jira)

James Perkins created WFCORE-4676: ------------------------------------- Summary: Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final Key: WFCORE-4676 URL: https://issues.jboss.org/browse/WFCORE-4676 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.14.Final to 2.1.15.Final. This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4675) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

by James Perkins (Jira)

James Perkins created WFCORE-4675: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final Key: WFCORE-4675 URL: https://issues.jboss.org/browse/WFCORE-4675 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.14.Final to 2.1.15.Final. This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4674?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4674: ---------------------------------- Labels: OpenShift jdk11 (was: jdk11) > 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.jboss.org/browse/WFCORE-4674 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > > 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.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-261) If a module is defined and the log manager is on boot class path the log manager will fail to configure

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-261?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-261: --------------------------------- Labels: jdk11 (was: ) > If a module is defined and the log manager is on boot class path the log manager will fail to configure > ------------------------------------------------------------------------------------------------------- > > Key: LOGMGR-261 > URL: https://issues.jboss.org/browse/LOGMGR-261 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: jdk11 > > If the log manager is on the boot class path and a module is defined in the {{logging.properties}} or defined in the configuration API the log manager will fail to configure. 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} > The only real resolution to this will be to create some kind of {{ModuleFinder}} API in the log manager which allows something like jboss-modules to implement a version which knows how to log the modules. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-261) If a module is defined and the log manager is on boot class path the log manager will fail to configure

by James Perkins (Jira)

James Perkins created LOGMGR-261: ------------------------------------ Summary: If a module is defined and the log manager is on boot class path the log manager will fail to configure Key: LOGMGR-261 URL: https://issues.jboss.org/browse/LOGMGR-261 Project: JBoss Log Manager Issue Type: Bug Components: core Reporter: James Perkins Assignee: James Perkins If the log manager is on the boot class path and a module is defined in the {{logging.properties}} or defined in the configuration API the log manager will fail to configure. 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} The only real resolution to this will be to create some kind of {{ModuleFinder}} API in the log manager which allows something like jboss-modules to implement a version which knows how to log the modules. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 James Perkins (Jira)

James Perkins created WFCORE-4674: ------------------------------------- Summary: 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.jboss.org/browse/WFCORE-4674 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins 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.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-245) In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact :jboss-servlet-api_4.0_spec

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/JBEE-245?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated JBEE-245: ------------------------------ Summary: In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact :jboss-servlet-api_4.0_spec (was: In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact ) > In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact :jboss-servlet-api_4.0_spec > --------------------------------------------------------------------------------------------------------------------- > > Key: JBEE-245 > URL: https://issues.jboss.org/browse/JBEE-245 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jakarta-jax-rpc-api > Reporter: Scott Marlow > Assignee: Jim Ma > Priority: Major > > Please update https://github.com/jboss/jboss-jakarta-jax-rpc-api/blob/master/api/pom.xm..., from: > {code} > <dependency> > <groupId>org.jboss.spec.javax.servlet</groupId> > <artifactId>jboss-servlet-api_3.1_spec</artifactId> > <version>1.0.2.Final</version> > <optional>true</optional> > </dependency> > {code} > To instead depend on org.jboss.spec.javax.servlet:jboss-servlet-api_4.0_spec:2.0.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-245) jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact

by Scott Marlow (Jira)

Scott Marlow created JBEE-245: --------------------------------- Summary: jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact Key: JBEE-245 URL: https://issues.jboss.org/browse/JBEE-245 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jakarta-jax-rpc-api Reporter: Scott Marlow Assignee: Jim Ma Please update https://github.com/jboss/jboss-jakarta-jax-rpc-api/blob/master/api/pom.xm..., from: {code} <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.1_spec</artifactId> <version>1.0.2.Final</version> <optional>true</optional> </dependency> {code} To instead depend on org.jboss.spec.javax.servlet:jboss-servlet-api_4.0_spec:2.0.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-245) In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/JBEE-245?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated JBEE-245: ------------------------------ Summary: In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact (was: jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact ) > In jboss-jakarta-jax-rpc-api pom.xml update dependency to use jboss-jakarta spec artifact > ------------------------------------------------------------------------------------------ > > Key: JBEE-245 > URL: https://issues.jboss.org/browse/JBEE-245 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jakarta-jax-rpc-api > Reporter: Scott Marlow > Assignee: Jim Ma > Priority: Major > > Please update https://github.com/jboss/jboss-jakarta-jax-rpc-api/blob/master/api/pom.xm..., from: > {code} > <dependency> > <groupId>org.jboss.spec.javax.servlet</groupId> > <artifactId>jboss-servlet-api_3.1_spec</artifactId> > <version>1.0.2.Final</version> > <optional>true</optional> > </dependency> > {code} > To instead depend on org.jboss.spec.javax.servlet:jboss-servlet-api_4.0_spec:2.0.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

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 September 2019