[JBoss JIRA] (LOGMGR-260) System loggers run with level ALL
by Philippe Marschall (Jira)
Philippe Marschall created LOGMGR-260:
-----------------------------------------
Summary: System loggers run with level ALL
Key: LOGMGR-260
URL: https://issues.jboss.org/browse/LOGMGR-260
Project: JBoss Log Manager
Issue Type: Bug
Components: core
Environment: Java 9+
Reporter: Philippe Marschall
After migrating to Java 11 we were suddenly seeing a lot of caught exceptions {{sun.rmi.runtime.Log#getSource()}}. This was surprising to use because we use WildFly which sets the "sun.rmi" logger to level WARN. Upon closer inspection the issue is that the logger used by {{sun.rmi.runtime.Log}} has level ALL ({{Integer#MIN_VALUE}}).
The issue for this seems to be the following:
# since Java 9 java.util.logging differentiates between system loggers (used by modules in the platform classloader) and user loggers (everything else), see {{java.util.logging#Logger.demandLogger(String, String, Class<?>)}}
# when a system logger is created a second user logger is created and their configurations merge, however they are merged based on internal state maintained by {{#setLevel(Level)}}, see {{java.util.logging.LogManager#demandSystemLogger(String, String, Module)}} and {{java.util.logging.Logger#mergeWithSystemLogger(Logger)}}
# {{org.jboss.logmanager.Logger}} only ends up calling {{#setLevel(Level)}} with {{Level.ALL}} therefore the resulting system logger always has the level ALL
The issue is quite hard to test because:
# the effect only happens when the caller of {{#getLoggger(String)}} is a system module
# the log output is not different, only {{#isLoggable(Level)}} checks that shouldn't succeed suddenly succeed so you only see the overhead
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (JBEE-232) Remove spec and use an aggregator for jboss-interceptors-api_1.2_spec
by Yeray Borges (Jira)
Yeray Borges created JBEE-232:
---------------------------------
Summary: Remove spec and use an aggregator for jboss-interceptors-api_1.2_spec
Key: JBEE-232
URL: https://issues.jboss.org/browse/JBEE-232
Project: JBoss Enterprise Spec APIs
Issue Type: Task
Reporter: Yeray Borges
Assignee: Yeray Borges
Jakarta project is organized in its root by a parent pom and two modules api and spec.
This task is to remove from our fork the parent pom and replace it by an aggregator and the spec module.
Maven deploy plugin must be skipped for the aggregator.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (JBEE-231) Remove spec and use an aggregator for jboss-annotations-api_1.3_spec
by Yeray Borges (Jira)
Yeray Borges created JBEE-231:
---------------------------------
Summary: Remove spec and use an aggregator for jboss-annotations-api_1.3_spec
Key: JBEE-231
URL: https://issues.jboss.org/browse/JBEE-231
Project: JBoss Enterprise Spec APIs
Issue Type: Bug
Components: jboss-annotations-api
Reporter: Yeray Borges
Assignee: Yeray Borges
Fix For: jboss-annotations-api_1.3_spec-2.0.0.Final
Jakarta project is organized in its root by a parent pom and two modules api and spec.
This task is to remove from our fork the parent pom and replace it by an aggregator and the spec module.
Maven deploy plugin must be skipped for the aggregator.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12495) Separate out feature groups related to clustering
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12495:
---------------------------------------
Summary: Separate out feature groups related to clustering
Key: WFLY-12495
URL: https://issues.jboss.org/browse/WFLY-12495
Project: WildFly
Issue Type: Sub-task
Components: Build System, Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 18.0.0.Final
The Galleon pack has a number of feature groups that incorporate in one group chunks of clustering-related config that are related to different use cases. Separate these out to make them useful for distinct layers related to those use cases.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12494) Add product maven repository to BOMs and Quickstarts
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-12494:
--------------------------------------
Summary: Add product maven repository to BOMs and Quickstarts
Key: WFLY-12494
URL: https://issues.jboss.org/browse/WFLY-12494
Project: WildFly
Issue Type: Feature Request
Components: BOM, Quickstarts
Reporter: Eduardo Martins
Assignee: Eduardo Martins
Product artifacts are now being used by WildFly, thus such repos are needed also in BOMs and Quickstarts parent poms.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months