July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5066) [QA] A few tests don't work using IBM JDK because of mock-server 5.9.0

by Panagiotis Sotiropoulos (Jira)

Panagiotis Sotiropoulos created WFCORE-5066: ----------------------------------------------- Summary: [QA] A few tests don't work using IBM JDK because of mock-server 5.9.0 Key: WFCORE-5066 URL: https://issues.redhat.com/browse/WFCORE-5066 Project: WildFly Core Issue Type: Bug Components: Test Suite Affects Versions: 13.0.0.Beta1 Reporter: Panagiotis Sotiropoulos Assignee: Ricardo Martin Camarero After JIRA WFCORE-4850 the mock-server 5.9.0 does not work with IBM JDK which makes a few tests fail with the following error: {code:bash} cd ./testsuite/standalone/ export JAVA_HOME=/home/rmartinc/apps/ibm-java-x86_64-80/ mvn clean test -Dtest=org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase ... [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.005 s <<< FAILURE! - in org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase [ERROR] org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: sun.security.x509.GeneralNameInterface at org.mockserver.socket.tls.jdk.JDKKeyAndCertificateFactory.<init>(JDKKeyAndCertificateFactory.java:36) at org.mockserver.socket.tls.NettySslContextFactory.<init>(NettySslContextFactory.java:37) at org.mockserver.client.MockServerClient.<init>(MockServerClient.java:57) at org.mockserver.integration.ClientAndServer.<init>(ClientAndServer.java:19) at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.setup(SecurityCommandsTestCase.java:358) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:157) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) Caused by: java.lang.ClassNotFoundException: sun.security.x509.GeneralNameInterface at java.net.URLClassLoader.findClass(URLClassLoader.java:610) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:944) at java.lang.ClassLoader.loadClass(ClassLoader.java:889) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:872) ... 36 more {code} The tests that don't work are the following three classes: * CertificateAuthoritiesTestCase.java (elytron) * KeyStoresTestCase.java (elytron) * SecurityCommandsTestCase.java (testsuite/standalone) This is explained in the mock-server [issue 750|https://github.com/mock-server/mockserver/issues/750]. For the moment the only solution is doing a downgrade to 5.8.1. Although it is expected to be fixed soon in the mock-server (maybe in the next version 5.10.1 or 5.11.0). -- 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 Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5535?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5535. --------------------------------- Resolution: Explained Kogito is a new business automation suite [https://kogito.kie.org/] It is cloud native and internally uses drools and jbpm respectively as rules and workflow engine. It is fully integrated with quarkus through a quarkus extension, see [https://quarkus.io/guides/kogito] and [https://developers.redhat.com/blog/2019/08/29/kogito-for-quarkus-intellig...] You can find many examples on how to use it with both quarkus and spring-boot here https://github.com/kiegroup/kogito-examples > 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] (WFLY-13705) Integrate server probes in MP Health readiness check

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13705: ---------------------------------- Summary: Integrate server probes in MP Health readiness check Key: WFLY-13705 URL: https://issues.redhat.com/browse/WFLY-13705 Project: WildFly Issue Type: Feature Request Components: MP Health Reporter: Jeff Mesnil Assignee: Jeff Mesnil MicroProfile Health 2.0 introduced a readiness health check. WFLY-12228 added support for MicroProfile Health 2.0 without enhancing the readiness health check. This RFE enhances it with 3 probes (that are part of the EAP readiness probe script at [1]): * server-status - returns UP when the server-state is READY * boot-errors - return UP if there are no boot-errors * deployment-status - returns UP if status for all deployments is OK [1] https://github.com/jboss-container-images/jboss-eap-modules/blob/251f422c... -- 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 Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5535?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5535: -------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > 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] (WFLY-13703) Increase the test coverage of LayersTestCase for the all layers case

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13703?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13703: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13429, https://github.com/wildfly/wildfly/pull/13432 (was: https://github.com/wildfly/wildfly/pull/13429) > 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 > Priority: Major > Fix For: 21.0.0.Beta1 > > > 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

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

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13703?page=com.atlassian.jira.plugi... ] Yeray Borges Santana reopened WFLY-13703: ----------------------------------------- > 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 > Priority: Major > Fix For: 21.0.0.Beta1 > > > 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

[JBoss JIRA] (DROOLS-5536) Not pattern dereferencing a variable in a constraint is wrongly evaluated using the executable model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5536?page=com.atlassian.jira.plug... ] Luca Molteni reassigned DROOLS-5536: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > Not pattern dereferencing a variable in a constraint is wrongly evaluated using the executable model > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-5536 > URL: https://issues.redhat.com/browse/DROOLS-5536 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Luca Molteni > Priority: Major > > Reproducer > {code:java} > @Test > public void testNotWithDereferencingConstraint() { > final String drl1 = > "package org.drools.compiler\n" + > "import " + Person.class.getCanonicalName() + ";\n" + > "rule R when\n" + > " $p: Person( $name : name )\n" + > " not Person( name.length == $name.length )\n" + > "then\n" + > "end\n"; > KieSession ksession = getKieSession( drl1 ); > ksession.insert( new Person("test", 18) ); > assertEquals( 0, ksession.fireAllRules() ); > } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5536) Not pattern dereferencing a variable in a constraint is wrongly evaluated using the executable model

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5536: ----------------------------------- Summary: Not pattern dereferencing a variable in a constraint is wrongly evaluated using the executable model Key: DROOLS-5536 URL: https://issues.redhat.com/browse/DROOLS-5536 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Reproducer {code:java} @Test public void testNotWithDereferencingConstraint() { final String drl1 = "package org.drools.compiler\n" + "import " + Person.class.getCanonicalName() + ";\n" + "rule R when\n" + " $p: Person( $name : name )\n" + " not Person( name.length == $name.length )\n" + "then\n" + "end\n"; KieSession ksession = getKieSession( drl1 ); ksession.insert( new Person("test", 18) ); assertEquals( 0, ksession.fireAllRules() ); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13697) JBoss CLI can't find java:app/AppName

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13697?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13697: ------------------------------------ Component/s: Batch Management (was: CLI) > JBoss CLI can't find java:app/AppName > ------------------------------------- > > Key: WFLY-13697 > URL: https://issues.redhat.com/browse/WFLY-13697 > Project: WildFly > Issue Type: Bug > Components: Batch, Management > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: José Fernando Tepedino Martins > Assignee: Michal Petrov > Priority: Minor > Labels: CLI, JNDI > > With a JEE aplication in a WAR package, when starting a functionality, as a Batch Job, via CLI, CDI injection and JNDI lookup fail to find resources 'java:app/AppName' and 'java:module/ModuleName'. > For example, a job listener or other job artifact with the following code > {code:java} > @Resource(lookup="java:app/AppName") > private String applicationName;{code} > or > {code:java} > private String applicationName; > @PostConstruct > protected void initialize() throws NamingException { > applicationName = InitialContext.doLookup("java:app/AppName"); > }{code} > when the batch job is started from JBoss CLI, the following error will be logged: > {code:java} > javax.naming.NameNotFoundException: java:app/AppName > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

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

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13704?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-13704: ------------------------------ Issue Type: Task (was: Component Upgrade) > Replace use of org.jboss.remoting3 module in tests > -------------------------------------------------- > > Key: WFLY-13704 > URL: https://issues.redhat.com/browse/WFLY-13704 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 20.0.1.Final > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > 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

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