May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5360) Replace KiePMMLModel with modelname in PMMLModelExecutor.evaluate

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5360: ---------------------------------------- Summary: Replace KiePMMLModel with modelname in PMMLModelExecutor.evaluate Key: DROOLS-5360 URL: https://issues.redhat.com/browse/DROOLS-5360 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Change PMMLModelExecutor public API so that user should not retrieve the KiePMMLModel to invoke the "evaluate" method {code:java} PMML4Result evaluate(final KieBase knowledgeBase, KiePMMLModel model, PMMLContext context) {code} -> {code:java} PMML4Result evaluate(final KieBase knowledgeBase, String modelName, PMMLContext context); {code} Create AbstractPMMLModelExecutor that implement the above interface and declare an abstract method {code:java} PMML4Result evaluate(final KieBase knowledgeBase, KiePMMLModel model, PMMLContext context) {code} AbstractPMMLModelExecutor should then use KnoweledgeBaseUtils to retrieve the KiePMMLModel and invoke/delegate to actual implementations Actual implementations should then extend AbstractPMMLModelExecutor -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1158) Mirror jaeger test environment images on disconnected environment

by Jeeva Kandasamy (Jira)

Jeeva Kandasamy created SWSQE-1158: -------------------------------------- Summary: Mirror jaeger test environment images on disconnected environment Key: SWSQE-1158 URL: https://issues.redhat.com/browse/SWSQE-1158 Project: Kiali QE Issue Type: Sub-task Reporter: Jeeva Kandasamy [~jkandasa] and [~kearls] will add the required images details here. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4980) Service definitions should be aggregated in shaded jars

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4980: ---------------------------------------- Summary: Service definitions should be aggregated in shaded jars Key: WFCORE-4980 URL: https://issues.redhat.com/browse/WFCORE-4980 Project: WildFly Core Issue Type: Bug Components: Build System, CLI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Many of our libraries rely heavily on ServiceLoader based discovery, where we also use shaded-jars we potentially aggregate multiple sources of the service definitions - we should be default aggregate these into the resulting jar. https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-tra... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1970) The service descriptors in the wildfly-elytron module do not correctly combine the other modules.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1970?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1970: ---------------------------------- Attachment: ELY-1970.txt > The service descriptors in the wildfly-elytron module do not correctly combine the other modules. > ------------------------------------------------------------------------------------------------- > > Key: ELY-1970 > URL: https://issues.redhat.com/browse/ELY-1970 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.12.0.CR3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.12.0.CR4 > > Attachments: ELY-1970.txt > > > At the moment it looks like it is some kind of first / last match wins rather than aggregating the names of the services. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1970) The service descriptors in the wildfly-elytron module do not correctly combine the other modules.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1970?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1970: --------------------------------------- The attached test file illustrates the difference in the resulting file. > The service descriptors in the wildfly-elytron module do not correctly combine the other modules. > ------------------------------------------------------------------------------------------------- > > Key: ELY-1970 > URL: https://issues.redhat.com/browse/ELY-1970 > Project: WildFly Elytron > Issue Type: Bug > Components: Build > Affects Versions: 1.12.0.CR3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.12.0.CR4 > > Attachments: ELY-1970.txt > > > At the moment it looks like it is some kind of first / last match wins rather than aggregating the names of the services. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5359) Verify KiePMMLSessionUtils.addObjectsToSession for Kogito

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5359: ---------------------------------------- Summary: Verify KiePMMLSessionUtils.addObjectsToSession for Kogito Key: DROOLS-5359 URL: https://issues.redhat.com/browse/DROOLS-5359 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Verify that KiePMMLSessionUtils.addObjectsToSession is working inside kogito (reflection usage) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Lukas Vydra commented on WFLY-10173: ------------------------------------ Hi [~cfang], I can confirm that the test is now stable even on Windows. Thank you (y) > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > 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:564) > 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.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-940) drools 6.3.0.Final 's kie.server.client did not work fine

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-940?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi closed DROOLS-940. ------------------------------------ Resolution: Explained > drools 6.3.0.Final 's kie.server.client did not work fine > --------------------------------------------------------- > > Key: DROOLS-940 > URL: https://issues.redhat.com/browse/DROOLS-940 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.CR1, 6.3.0.CR2, 6.3.0.Final > Environment: WIN 7 TOMCAT8 > wildfly-8.2.1.Final > Reporter: Kevin Xu > Assignee: Maciej Swiderski > Priority: Major > > KieServicesConfiguration config = KieServicesFactory.newRestConfiguration( > "http://localhost:8230/kie-server/services/rest/server", "kieserver", "kieserver1!"); > config.setMarshallingFormat(MarshallingFormat.XSTREAM); > KieServicesClient client = KieServicesFactory.newKieServicesClient(config); > > System.out.println(xStreamXml); > > // "ListenerReproducer" is the name of the Container > ServiceResponse<String> response = client.executeCommands("mortgages", xStreamXml); > THE CODE CAN NOT WORK IN 6.3 FINAL,but it can work in 6.3 rc2 > because the container's POST URI is changed > http://localhost:8230/kie-server/services/rest/server/containers/instance... > there is a "instances" behind the containers -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1003) incongruous security granularity in kie-server

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-1003?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-1003: ------------------------------------------- Hi David, Sorry about not responding on this JIRA. This JIRA seems to be still a valid request in RHDM/RHPAM 7.x. Do you still request this from cloud point of view? Please kindly confirm. > incongruous security granularity in kie-server > ---------------------------------------------- > > Key: DROOLS-1003 > URL: https://issues.redhat.com/browse/DROOLS-1003 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.Final > Reporter: David Ward > Assignee: Maciej Swiderski > Priority: Major > Attachments: web.xml > > > The KIE Server provides two endpoints: HTTP/REST and JMS. By default, there is a "kie-server" role that one must have to perform operations through either endpoint. But by having this role, you can do *anything* in a very coarse-grained fashion. > Luckily, the HTTP/REST endpoint can be modified by changing the kie-server.war/WEB-INF/web.xml, and adding/modifying the security constraints. For OpenShift purposes, this has been done to disallow creating and disposing containers, while still allowing for reading status and executing rules. This is because REST url-patterns can be filtered per various operations and also with different http-methods. (See attached web.xml for an example.) > However, the JMS endpoint has no such capability. There is only one request queue with appserver security on it on a coarse-grained level, and no way to filter the messages as can be done via the HTTP/REST endpoint. > I have an idea that might help? Clients invoke the server via serializing and sending in Command objects, and those objects themselves are fine-grained (they are named things like "CallContainerCommand" and "DisposeContainerCommand"). If the incoming messages could propagate some kind of property of who the caller was, then the server-side could do a isCallerInRole/isUserInRole to determine if that user is authorized to invoke that particular command before doing so. Just a brainstorming idea. > Here is an example of the server handling the commands: > https://github.com/droolsjbpm/droolsjbpm-integration/blob/6.2.x/kie-serve... > The desired goal would be that developers (like myself) would not have to edit the kie-server.war/WEB-INF/web.xml, and that the same level of security granularity would already be available out-of-the-box for both the HTTP/REST and JMS interfaces. All that would be left for us would be to grant users the appropriate roles. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1004) classloading errors in kie-server

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-1004?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-1004: ------------------------------------------- Hi, Do you still have the issue? Or can we close this JIRA as Out of Date? > classloading errors in kie-server > --------------------------------- > > Key: DROOLS-1004 > URL: https://issues.redhat.com/browse/DROOLS-1004 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.3.0.Final > Reporter: David Ward > Assignee: Maciej Swiderski > Priority: Major > > There appear to be some classloading errors in kie-server.war 6.3.0.Final-redhat-5 being deployed on JBoss EAP 6.4.4. > *First, you get multiple jaxb and parser warnings like this:* > {code} > 11:58:47,603 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-api.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference. > 11:58:47,606 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-core.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference. > 11:58:47,644 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-core.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference. > 11:58:47,644 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb-impl.jar in /opt/eap/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference. > 11:58:47,713 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory' > {code} > The above was noticed as part of CLOUD-421. Please refer to the jira issue and note Kev's comment, {quote}"The jaxb jars are duplicates that are unnecessary in the EAP deployments however the upstream war file contains all dependencies. Removing the jaxb jars from within the kie-server.war/WEB-INF/lib directory will likely work however I'm loathed to do this since we would need to verify this through the BRMS QE team. > The warning about the parser is caused by the kie-server.war/WEB-INF/lib/xpp3_min-1.1.4c.jar"{quote} > *Second, there can be missing osgi classes:* > If kjar model classes contain certain annotations, it seems to trigger the kie-server to try to load osgi classes. For example, annotating kjar model classes with Position, PropertyReactive, and Remotable as per this test case: > http://git.app.eng.bos.redhat.com/git/xpaas-qe.git/tree/test-brms/src/tes... > , you end up with errors like this in the log when the KieContainer is being installed: > {code} > Caused by: java.lang.NoClassDefFoundError: org/osgi/util/tracker/ServiceTrackerCustomizer > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0_65] > at java.lang.ClassLoader.defineClass(ClassLoader.java:760) [rt.jar:1.8.0_65] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.7.Final-redhat-1] > ... 77 more > Caused by: java.lang.ClassNotFoundException: org.osgi.util.tracker.ServiceTrackerCustomizer from [Module "deployment.kie-server.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1] > ... 81 more > {code} > The above was noticed as part of CLOUD-418. To get around this issue, I had to add a kie-server.war/WEB-INF/jboss-deployment-structure.xml like so: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure> > <deployment> > <dependencies> > <module name="org.osgi.core"/> > <module name="org.osgi.enterprise"/> > </dependencies> > </deployment> > </jboss-deployment-structure> > {code} > The jboss-bpmsuite-6.2.0.GA-redhat-1-deployable-eap6.x.zip file (from which we extract the kie-sever.war) is seemingly an EAP-specific build (thus the -eap6.x suffix). So perhaps the fix would be to have the kie-server.war already come pre-configured to contain (or better yet, depend upon the existing modules) jars in EAP for both the above problems (incorrect jaxb/xmlpull references, and missing osgi dependencies). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 May 2020