July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13667) Prometheus JMX exporter jar, stops starting the wildfly server.

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13667?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-13667: -------------------------------------- [~rakesh.shah1977] Okay so I'm not sure why, but if you add {{-Djava.util.logging.manager=org.jboss.logmanager.LogManager}} as the first argument it seems to work. {code} set "-Djava.util.logging.manager=org.jboss.logmanager.LogManager JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/a:%JBOSS_HOME%\modules\system\layers\base\org\jboss\logmanager\main\jboss-logmanager-2.1.15.Final.jar;%JBOSS_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.5.4.Final.jar -javaagent:%JBOSS_HOME%\jmx_prometheus_javaagent-0.13.0.jar=9080:%JBOSS_HOME%\standalone\configuration\config.yaml" {code} Note the only difference in my snippet is the placement of setting the log manager and I put the configuration in the {{standalone}} configuration directory. > Prometheus JMX exporter jar, stops starting the wildfly server. > ---------------------------------------------------------------- > > Key: WFLY-13667 > URL: https://issues.redhat.com/browse/WFLY-13667 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 20.0.1.Final > Reporter: Rakesh Kumar Shah > Assignee: James Perkins > Priority: Major > > Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception. > {code} > java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239) > at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223) > at java.base/java.security.AccessController.doPrivileged(Native Method) > at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223) > at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648) > at java.logging/java.util.logging.Logger.getLogger(Logger.java:717) > at java.logging/java.util.logging.Logger.getLogger(Logger.java:701) > at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39) > at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) > at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) > WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level > at java.base/java.lang.Class.forName0(Native Method) > at java.base/java.lang.Class.forName(Class.java:398) > at org.jboss.modules.Module.run(Module.java:340) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:617) > Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level > at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) > at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-144) Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles

by dy valverdes (Jira)

[ https://issues.redhat.com/browse/JBLOGGING-144?page=com.atlassian.jira.pl... ] dy valverdes commented on JBLOGGING-144: ---------------------------------------- Thank you for the quick reply. We use Apache Ant 1.10.8 to build our application but we hit that error mentioned in the description. {noformat} [artifact:dependencies] An error has occurred while processing the Maven artifact tasks. [artifact:dependencies] Diagnosis: [artifact:dependencies] [artifact:dependencies] Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent [artifact:dependencies] org.jboss.logging:jboss-logging:jar:3.4.1.Final {noformat} > Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles > ---------------------------------------------------------------------------- > > Key: JBLOGGING-144 > URL: https://issues.redhat.com/browse/JBLOGGING-144 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: dy valverdes > Assignee: James Perkins > Priority: Major > > Hello, > jboss-parent 34 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' > [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] > > This is preventing Ant from building > {noformat} > Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent > {noformat} > It has been fixed in jboss-parent 36 > [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] > > Kind regards, > dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5508) [DMN Designer] PMML: improve the data type handling

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-5508?page=com.atlassian.jira.plug... ] Edson Tirelli reassigned DROOLS-5508: ------------------------------------- Assignee: Guilherme Gomes (was: Edson Tirelli) > [DMN Designer] PMML: improve the data type handling > --------------------------------------------------- > > Key: DROOLS-5508 > URL: https://issues.redhat.com/browse/DROOLS-5508 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.39.0.Final > Reporter: Donato Marrazzo > Assignee: Guilherme Gomes > Priority: Minor > > At the moment, PMML data type are disregarded when the DMN Editor imports it (they becomes "Any" data type). > In PMML the data dictionary provides valuable information about the input and output parameters. E.g. > {code:java} > <DataField name="category" optype="continuous" dataType="double"/>{code} > It would be useful to correctly map them. > > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-144) Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles

by James Perkins (Jira)

[ https://issues.redhat.com/browse/JBLOGGING-144?page=com.atlassian.jira.pl... ] James Perkins commented on JBLOGGING-144: ----------------------------------------- I've got no objection with upgrading the parent component, but what is the issue with this? In other words how are you using this that causes this issue? > Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles > ---------------------------------------------------------------------------- > > Key: JBLOGGING-144 > URL: https://issues.redhat.com/browse/JBLOGGING-144 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: dy valverdes > Assignee: James Perkins > Priority: Major > > Hello, > jboss-parent 34 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' > [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] > > This is preventing Ant from building > {noformat} > Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent > {noformat} > It has been fixed in jboss-parent 36 > [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] > > Kind regards, > dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5508) [DMN Designer] PMML: improve the data type handling

by Donato Marrazzo (Jira)

Donato Marrazzo created DROOLS-5508: --------------------------------------- Summary: [DMN Designer] PMML: improve the data type handling Key: DROOLS-5508 URL: https://issues.redhat.com/browse/DROOLS-5508 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.39.0.Final Reporter: Donato Marrazzo Assignee: Edson Tirelli At the moment, PMML data type are disregarded when the DMN Editor imports it (they becomes "Any" data type). In PMML the data dictionary provides valuable information about the input and output parameters. E.g. {code:java} <DataField name="category" optype="continuous" dataType="double"/>{code} It would be useful to correctly map them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13668) Upgrade jboss-parent to 36

by dy valverdes (Jira)

dy valverdes created WFLY-13668: ----------------------------------- Summary: Upgrade jboss-parent to 36 Key: WFLY-13668 URL: https://issues.redhat.com/browse/WFLY-13668 Project: WildFly Issue Type: Component Upgrade Reporter: dy valverdes Assignee: Brian Stansberry Hello, jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] This is preventing Ant from building: {noformat} Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.wildfly.common:wildfly-common:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent {noformat} It has been fixed in jboss-parent 36 [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss...] Kind regards, dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4196) [DMN Designer] PMML: Show default when document has no explicit model

by Donato Marrazzo (Jira)

[ https://issues.redhat.com/browse/DROOLS-4196?page=com.atlassian.jira.plug... ] Donato Marrazzo commented on DROOLS-4196: ----------------------------------------- I think that whether modelName is absent, the tool should name it using the generic name plus a progressive number. e.g. from this pmml: {code:java} <RegressionModel ....> <RegressionModel ....> <NearestNeighborModel ...> {code} the drop down list should show: * RegressionModel 1 * RegressionModel 2 * NearestNeighborModel 1 > [DMN Designer] PMML: Show default when document has no explicit model > --------------------------------------------------------------------- > > Key: DROOLS-4196 > URL: https://issues.redhat.com/browse/DROOLS-4196 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Edson Tirelli > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > If the PMML file contains no "named" model (only an anonymous one), the UI should indicate that this model is being used (how to indicate that I leave to UX, but we can call it "default model" or whatever). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-144) Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles

by dy valverdes (Jira)

[ https://issues.redhat.com/browse/JBLOGGING-144?page=com.atlassian.jira.pl... ] dy valverdes updated JBLOGGING-144: ----------------------------------- Description: Hello, jboss-parent 34 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] This is preventing Ant from building {noformat} Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent {noformat} It has been fixed in jboss-parent 36 [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] Kind regards, dy was: Hello, jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] This is preventing Ant from building {noformat} Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent {noformat} It has been fixed in jboss-parent 36 [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] Kind regards, dy > Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles > ---------------------------------------------------------------------------- > > Key: JBLOGGING-144 > URL: https://issues.redhat.com/browse/JBLOGGING-144 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: dy valverdes > Assignee: James Perkins > Priority: Major > > Hello, > jboss-parent 34 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' > [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] > > This is preventing Ant from building > {noformat} > Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent > {noformat} > It has been fixed in jboss-parent 36 > [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] > > Kind regards, > dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-144) Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles

by dy valverdes (Jira)

[ https://issues.redhat.com/browse/JBLOGGING-144?page=com.atlassian.jira.pl... ] dy valverdes updated JBLOGGING-144: ----------------------------------- Description: Hello, jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] This is preventing Ant from building {noformat} Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent {noformat} It has been fixed in jboss-parent 36 [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] Kind regards, dy was: Hello, jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] This is preventing Ant from building {noformat} Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent {noformat} It has been fixed in jboss-parent 36 [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss...] Kind regards, dy > Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles > ---------------------------------------------------------------------------- > > Key: JBLOGGING-144 > URL: https://issues.redhat.com/browse/JBLOGGING-144 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: dy valverdes > Assignee: James Perkins > Priority: Major > > Hello, > jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' > [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] > > This is preventing Ant from building > {noformat} > Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent > {noformat} > It has been fixed in jboss-parent 36 > [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-34...jboss...] > > Kind regards, > dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-144) Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles

by dy valverdes (Jira)

[ https://issues.redhat.com/browse/JBLOGGING-144?page=com.atlassian.jira.pl... ] dy valverdes updated JBLOGGING-144: ----------------------------------- Summary: Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles (was: Upgrade jboss-parent to version 36 as 35 has unbounded range in all profiles) > Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles > ---------------------------------------------------------------------------- > > Key: JBLOGGING-144 > URL: https://issues.redhat.com/browse/JBLOGGING-144 > Project: JBoss Logging > Issue Type: Feature Request > Reporter: dy valverdes > Assignee: James Perkins > Priority: Major > > Hello, > jboss-parent 35 has an unbounded range in all profiles, like '[9,' in 'compile-java8-release-flag' > [https://github.com/jboss/jboss-parent-pom/blob/246dd07b95c69680f3104ec360...] > > This is preventing Ant from building > {noformat} > Unable to resolve artifact: Unable to get dependency information: Unable to read the metadata file for artifact 'org.jboss.logging:jboss-logging:jar': Invalid JDK version in profile 'compile-java8-release-flag': Unbounded range: [9, for project org.jboss:jboss-parent > {noformat} > It has been fixed in jboss-parent 36 > [https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss...] > > Kind regards, > dy -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 July 2020