July 2020 - jboss-jira - Jboss List Archives

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

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ] James Perkins moved WFLY-13667 to WFCORE-5053: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-5053 (was: WFLY-13667) Component/s: Logging (was: Logging) Affects Version/s: (was: 20.0.1.Final) > Prometheus JMX exporter jar, stops starting the wildfly server. > ---------------------------------------------------------------- > > Key: WFCORE-5053 > URL: https://issues.redhat.com/browse/WFCORE-5053 > Project: WildFly Core > Issue Type: Bug > Components: Logging > 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)

6 years

1
0
0 / 0

[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: -------------------------------------- Well that's because I had it wrong so no wonder it worked :) Sorry about that. I'm not really too sure what is going on here. This works on Linux so I'm not sure why it's not working on Windows. I'll have to see if I can debug it on my Windows VM to see what's happening. > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10073) Key requester node_X is not in current view Y; ignoring key request

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-10073?page=com.atlassian.jira.plugi... ] Paul Ferraro resolved WFLY-10073. --------------------------------- Fix Version/s: 20.0.0.Final Resolution: Out of Date > Key requester node_X is not in current view Y; ignoring key request > ------------------------------------------------------------------- > > Key: WFLY-10073 > URL: https://issues.redhat.com/browse/WFLY-10073 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Daniel Cihak > Assignee: Paul Ferraro > Priority: Major > Labels: clustering_revalidate > Fix For: 20.0.0.Final > > > Four errors were logged on *server* during failover scenario *eap-7x-failover-http-session-shutdown-dist-async-auth-asymEncrypt* (scenario with "AUTH" and "ASYM_ENCRYPT" protocols enabled) during new cluster view receiving: > {code} > 04:47:29,691 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-7,ee,perf21) ISPN000094: Received new cluster view for channel ejb: [perf21|8] (3) [perf21, perf18, perf19] > [JBossINF] 04:47:29,692 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) perf21: unrecognized cipher; discarding message from perf20 > [JBossINF] 04:47:29,692 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-9,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request > [JBossINF] 04:47:29,692 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request > [JBossINF] 04:47:29,694 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-13,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request > [JBossINF] 04:47:29,694 ERROR [org.jgroups.protocols.ASYM_ENCRYPT] (thread-13,ee,perf21) key requester perf20 is not in current view [perf21|8] (3) [perf21, perf18, perf19]; ignoring key request > [JBossINF] 04:48:37,553 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-2,ee,perf21) ISPN000094: Received new cluster view for channel server: [perf21|9] (4) [perf21, perf18, perf19, perf20] > {code} > WARN message was logged just before: > {code} > 04:47:29,692 WARN [org.jgroups.protocols.ASYM_ENCRYPT] (thread-1,ee,perf21) perf21: unrecognized cipher; discarding message from perf20 > {code} > Link to server log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov... > There are two WARN exceptions logged on client at the same time: > {code} > 04:47:28:988 EST [WARN ][Runner - 1066] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html>> > org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: <html><head><title>Error</title></head><body>Internal Server Error</body></html> > at org.jboss.smartfrog.loaddriver.http.HttpRequestProcessorFactoryImpl$HttpRequestProcessor.processRequest(HttpRequestProcessorFactoryImpl.java:163) > at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:52) > at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:103) > at java.lang.Thread.run(Thread.java:745) > {code} > Link to client log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failov... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13671) Revert temporary commit to mark "org.jboss.as.security-integration" as unused module.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13671?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFCORE-5052 to WFLY-13671: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13671 (was: WFCORE-5052) Component/s: Test Suite (was: Test Suite) Fix Version/s: 21.0.0.Beta1 (was: 13.0.0.Beta2) > Revert temporary commit to mark "org.jboss.as.security-integration" as unused module. > ------------------------------------------------------------------------------------- > > Key: WFLY-13671 > URL: https://issues.redhat.com/browse/WFLY-13671 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5052) Revert temporary commit to mark "org.jboss.as.security-integration" as unused module.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-5052: ---------------------------------------- Summary: Revert temporary commit to mark "org.jboss.as.security-integration" as unused module. Key: WFCORE-5052 URL: https://issues.redhat.com/browse/WFCORE-5052 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 13.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5509) Date field in Guided rule template is not displaying correct date

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5509: ------------------------------------ Summary: Date field in Guided rule template is not displaying correct date Key: DROOLS-5509 URL: https://issues.redhat.com/browse/DROOLS-5509 Project: Drools Issue Type: Bug Components: Guided Template Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13586) Add a Galleon layer for JSON-B

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13586?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13586: ---------------------------------------- Summary: Add a Galleon layer for JSON-B (was: Add a Galleon layer for JSONB) > Add a Galleon layer for JSON-B > ------------------------------ > > Key: WFLY-13586 > URL: https://issues.redhat.com/browse/WFLY-13586 > Project: WildFly > Issue Type: Feature Request > Components: Build System > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > Create a Galleon layer to provision JsonB API and Impl modules. > These modules are optionally provisioned by jaxrs, jaxrs-server and cloud-server. We can use this layer to add them on top of any other layer, or provision them even if optional dependencies are excluded. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 edited comment on JBLOGGING-144 at 7/15/20 7:04 AM: ----------------------------------------------------------------- Thank you for the suggestion. Unfortunately it doesn't work. The unbounded range declared in jboss-parent 34 (and 35, but fixed in 36) is invalid for Maven [https://maven.apache.org/ref/3.6.3/xref/org/apache/maven/artifact/version...] was (Author: dyvalverdes): Thank you for the suggestion. Unfortunately it doesn't work. > 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)

6 years

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 suggestion. Unfortunately it doesn't work. > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13670: ---------------------------------- Fix Version/s: 21.0.0.Beta1 > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 21.0.0.Beta1 > > > The 2 issues remaining are: > (5) Prerequisites and System Requirements sections both mention JDK and Maven versions. While JDK is just a duplicate, Maven version does not match in two sections. If the Maven version in standard System Requirements section is too old we should consider updating it. > (6) Build and Deploy the Quickstart section says "Make sure you start the JBoss EAP XP server as described above." and points to Start the JBoss EAP XP Standalone Server but this section is not above but below. > Suggestion: move Start the JBoss EAP XP Standalone Server above Build and Deploy the Quickstart and then you can point to this section from Creating the Maven Project from sentence "Start a JBoss EAP XP instance using the microprofile server profile." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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