July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13704) Replace use of org.jboss.remoting3 module in tests

by Cheng Fang (Jira)

Cheng Fang created WFLY-13704: --------------------------------- Summary: Replace use of org.jboss.remoting3 module in tests Key: WFLY-13704 URL: https://issues.redhat.com/browse/WFLY-13704 Project: WildFly Issue Type: Component Upgrade Components: Test Suite Affects Versions: 20.0.1.Final Reporter: Cheng Fang Assignee: Cheng Fang Fix For: 21.0.0.Beta1 some tests use org.jboss.remoting3 as its dependency, which is a deprecated module. for ex: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... Cheng Fang: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... remoting3 module: {code:xml} <module name="org.jboss.remoting3" xmlns="urn:jboss:module:1.5">    <resources> </resources> <dependencies> <module name="org.jboss.remoting" export="true"/> </dependencies> </module> {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5535) Drools - KieServices.Factory.get() returns null

by Ashish Srivastava (Jira)

[ https://issues.redhat.com/browse/DROOLS-5535?page=com.atlassian.jira.plug... ] Ashish Srivastava commented on DROOLS-5535: ------------------------------------------- I am trying multiple solutions which are mentioned in StackOverflow [https://stackoverflow.com/questions/47556233/drools-7-4-1-kieservices-fac...] [https://stackoverflow.com/questions/60971872/kieservices-kieservices-kies...] [https://stackoverflow.com/questions/47332148/nullpointer-in-kieservices-f...] [https://stackoverflow.com/questions/50258016/running-drools-as-a-fat-jarc...] [https://stackoverflow.com/questions/50258016/running-drools-as-a-fat-jarc...] [https://stackoverflow.com/questions/46690139/exception-child-services-hav...] > Drools - KieServices.Factory.get() returns null > ----------------------------------------------- > > Key: DROOLS-5535 > URL: https://issues.redhat.com/browse/DROOLS-5535 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.36.0.Final > Reporter: Ashish Srivastava > Assignee: Mario Fusco > Priority: Major > > I try to integrate a Drools project in a maven application. The Drools app is running perfectly on his own, but when I try to integrate it in the *quarkus project*, I get a java.lang.NullPointerException. > After some researches, it seems to happen because KieServices.Factory.get() return me null because of kie.conf. > Drools Site Quote is: Many modules of Drools (e.g. drools-core, drools-compiler) have a file named {{kie.conf}} containing the names of the classes implementing the services provided by the corresponding module. When running Drools in a fat JAR, for example created by the Maven Shade Plugin, those various {{kie.conf}} files need to be merged, otherwise , the fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. You can merge resources in the Maven Shade Plugin using transformers, like this: > ([https://docs.jboss.org/drools/release/7.14.0.Final/drools-docs/html_singl...]) > how can we configure the same for Quarkus Project ? or is there any way to load these file externally .. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5535) Drools - KieServices.Factory.get() returns null

by Ashish Srivastava (Jira)

Ashish Srivastava created DROOLS-5535: ----------------------------------------- Summary: Drools - KieServices.Factory.get() returns null Key: DROOLS-5535 URL: https://issues.redhat.com/browse/DROOLS-5535 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.36.0.Final Reporter: Ashish Srivastava Assignee: Mario Fusco I try to integrate a Drools project in a maven application. The Drools app is running perfectly on his own, but when I try to integrate it in the *quarkus project*, I get a java.lang.NullPointerException. After some researches, it seems to happen because KieServices.Factory.get() return me null because of kie.conf. Drools Site Quote is: Many modules of Drools (e.g. drools-core, drools-compiler) have a file named {{kie.conf}} containing the names of the classes implementing the services provided by the corresponding module. When running Drools in a fat JAR, for example created by the Maven Shade Plugin, those various {{kie.conf}} files need to be merged, otherwise , the fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. You can merge resources in the Maven Shade Plugin using transformers, like this: ([https://docs.jboss.org/drools/release/7.14.0.Final/drools-docs/html_singl...]) how can we configure the same for Quarkus Project ? or is there any way to load these file externally .. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5065) Add a hook for deployment transformation

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5065: ---------------------------------------- Summary: Add a hook for deployment transformation Key: WFCORE-5065 URL: https://issues.redhat.com/browse/WFCORE-5065 Project: WildFly Core Issue Type: Enhancement Components: Deployment Scanner, Server Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta3 Add an interface that the deployment scanner and DeploymentAddHandler can invoke to transform deployments from EE 8 to EE 9. Add an optional module dependency for the respective modules to provide an impl. Having this in core ASAP will dists based on WF Core that want to provide an impl to do some without requiring core to provide this itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5065) Add a hook for deployment transformation

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5065?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5065: ------------------------------------- Labels: EE9 (was: ) > Add a hook for deployment transformation > ---------------------------------------- > > Key: WFCORE-5065 > URL: https://issues.redhat.com/browse/WFCORE-5065 > Project: WildFly Core > Issue Type: Enhancement > Components: Deployment Scanner, Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: EE9 > Fix For: 13.0.0.Beta3 > > > Add an interface that the deployment scanner and DeploymentAddHandler can invoke to transform deployments from EE 8 to EE 9. Add an optional module dependency for the respective modules to provide an impl. > Having this in core ASAP will dists based on WF Core that want to provide an impl to do some without requiring core to provide this itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13546) Upgrade smallrye-open-api to 2.0.5

by Paul Ferraro (Jira)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13546) Upgrade smallrye-open-api to 2.0.5

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13546?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13546: -------------------------------- Description: Fixes: [https://github.com/smallrye/smallrye-open-api/issues/349] [https://github.com/smallrye/smallrye-open-api/issues/353] [https://github.com/smallrye/smallrye-open-api/issues/359] Release notes: [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.0] [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.1|https://...] [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.2|https://...] [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.3|https://...] [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.4|https://...] [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.5|https://...] was: Fixes: [https://github.com/smallrye/smallrye-open-api/issues/349] [https://github.com/smallrye/smallrye-open-api/issues/353] [https://github.com/smallrye/smallrye-open-api/issues/359] > Upgrade smallrye-open-api to 2.0.5 > ---------------------------------- > > Key: WFLY-13546 > URL: https://issues.redhat.com/browse/WFLY-13546 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Fixes: > [https://github.com/smallrye/smallrye-open-api/issues/349] > [https://github.com/smallrye/smallrye-open-api/issues/353] > [https://github.com/smallrye/smallrye-open-api/issues/359] > > Release notes: > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.0] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.1|https://...] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.2|https://...] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.3|https://...] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.4|https://...] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.5|https://...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13546) Upgrade smallrye-open-api to 2.0.5

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13546?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13546: -------------------------------- Summary: Upgrade smallrye-open-api to 2.0.5 (was: Upgrade smallrye-open-api to 2.0.3) > Upgrade smallrye-open-api to 2.0.5 > ---------------------------------- > > Key: WFLY-13546 > URL: https://issues.redhat.com/browse/WFLY-13546 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Fixes: > [https://github.com/smallrye/smallrye-open-api/issues/349] > [https://github.com/smallrye/smallrye-open-api/issues/353] > [https://github.com/smallrye/smallrye-open-api/issues/359] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[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 commented on WFCORE-5053: --------------------------------------- [~rakesh.shah1977] Currently there is no way to get a patch for it. For WildFly there is only community support so any patching would need to be done on your own :) Also since this was considered a feature as it changed behavior it will not be in JBoss EAP until 7.4. > 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 > Fix For: 13.0.0.Beta1 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13703) Increase the test coverage of LayersTestCase for the all layers case

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13703: ------------------------------------------- Summary: Increase the test coverage of LayersTestCase for the all layers case Key: WFLY-13703 URL: https://issues.redhat.com/browse/WFLY-13703 Project: WildFly Issue Type: Task Components: Build System, Test Suite Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana The LayersTestCase verifies the following: * Verifies the provisioned modules are the expected ones. * Verifies the provisioned server starts successfully. Currently, we have a server provision under test that doesn't add all the layers, the idea of this task is to supply one server provisioning including all the available layers. The WildFly Galleon Layers have an inheritance structure where some layers already include others, instead of check what is already included, the idea on this task is to include all, even if they are already included by another one, Galleon will take care of merging them. In the future, when a new layer is added, we have to add to this all-in-one provision. The idea is to have one all-in-one provision for jpa and all-in-one provision for jpa-distribute. The similar task could be done if we detect additional mutually excludable layers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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