July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4255) Add KIE server support for deploying custom Prometheus metrics

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4255?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-4255: ------------------------------------------- Fix Version/s: 7.25.0.Final (was: 7.24.0.Final) > Add KIE server support for deploying custom Prometheus metrics > -------------------------------------------------------------- > > Key: DROOLS-4255 > URL: https://issues.jboss.org/browse/DROOLS-4255 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.24.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Labels: CustomerFocus > Fix For: 7.25.0.Final > > > The first implementation of Prometheus support in Kie provided default Prometheus metrics. We should enable our users to deploy their custom Prometheus metrics in addition to default Prometheus metrics already published. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] (DEV) Add visual indicators for imported Nodes

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3907?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3907: ------------------------------------------- Fix Version/s: 7.25.0.Final (was: 7.24.0.Final) > [DMN Designer] (DEV) Add visual indicators for imported Nodes > ------------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.jboss.org/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.25.0.Final > > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4307) Drools unable to compile rules when using a declared enum in the DRL file

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4307?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-4307: --------------------------------- Sprint: 2019 Week 29-31 > Drools unable to compile rules when using a declared enum in the DRL file > ------------------------------------------------------------------------- > > Key: DROOLS-4307 > URL: https://issues.jboss.org/browse/DROOLS-4307 > Project: Drools > Issue Type: Bug > Reporter: Robert Buchmann > Assignee: Luca Molteni > Priority: Major > Attachments: drl.zip > > > I am finding inconsistent behaviour between drools reading rules from a local file (as a fileSystemResource) as opposed to pre compiling the rules into a kjar. > This happens if I use an enum declared within the drl file in the "when" or "then" section of a rule within the same drl file. > The rule runs perfectly as expected if I load the rule from the filesystem, but fails to run if I have pre-compiled the rule. For this reason I think this is a bug as I would expect the same behaviour for both ways of running rules. > I outlined the problem in more detail stackoverflow: > https://stackoverflow.com/questions/56989080/drools-maven-plugin-not-unde... > This is running JAVA8 and drools 7.23.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-824) UI Automations - Fix random failures for OCP4

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-824: ------------------------------------ Summary: UI Automations - Fix random failures for OCP4 Key: SWSQE-824 URL: https://issues.jboss.org/browse/SWSQE-824 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Li Xiankun (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Li Xiankun updated DROOLS-4257: ------------------------------- Description: Related to https://issues.jboss.org/browse/DROOLS-3731 This task will cover this use case: - user creates a DMN model - user creates a Test Scenario with some scenarios - user executes the Test Scenario - user open Coverage Report - user wants to analyze coverage information of {color:red}the *whole* simulation{color} - user clicks on "a link" near global coverage information - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) was: Related to https://issues.jboss.org/browse/DROOLS-3731 This task will cover this use case: - user creates a DMN model - user creates a Test Scenario with some scenarios - user executes the Test Scenario - user open Coverage Report - user wants to analyze coverage information of the *whole* simulation - user clicks on "a link" near global coverage information - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of {color:red}the *whole* simulation{color} > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3255) Complex type AttributeDefinition variants don't handle ParameterCorrector properly

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-3255?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3255: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3860 > Complex type AttributeDefinition variants don't handle ParameterCorrector properly > ---------------------------------------------------------------------------------- > > Key: WFCORE-3255 > URL: https://issues.jboss.org/browse/WFCORE-3255 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 3.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > If a field in a complex attribute (i.e. one that uses Object...AttributeDefinition) has a ParameterCorrector configured, that corrector never gets called. That's because only a corrector on the top level attribute gets called. > These classes should automatically use an internal corrector that first calls any corrector configured for fields, and then, if one is present, calls any top level corrector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-12182. ------------------------------------- Fix Version/s: 18.0.0.Beta1 Resolution: Done The WFCORE fix in 10.0.0.Beta1 did indeed fix it. > Resolve failure with EAP 7.2 mixed domain tests on JDK 12 > --------------------------------------------------------- > > Key: WFLY-12182 > URL: https://issues.jboss.org/browse/WFLY-12182 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Major > Fix For: 18.0.0.Beta1 > > > The EAP 7.2 mixed domain tests have been failing with JDK 12 since May 1. Task is to figure out why. > The changes that went into master before the first failure are here: > https://ci.wildfly.org/viewLog.html?buildId=148651&buildTypeId=WF_MasterL... > Note this includes a WildFly Core upgrade, so that could include all sorts of things. > The mixed domain runs report 12 failures, but the non-EAP 7.2 ones looks to be just because the 7.2 problems mess up the test env state, breaking later tests. This is something we've always seen. > The failure occurs when starting the legacy Process Controller: > {code} > &amp#27;[0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001 > &amp#27;[0m&amp#27;[33m05:12:02,692 WARN [org.jboss.modules.define] (main) Failed to define class org.jboss.logging.MDC in Module "org.jboss.logging" version 3.3.2.Final-redhat-00001 from local module loader @2ddc9a9f (finder: local module finder @298a5e20 (roots: /store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/slave/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules/system/layers/base)): org.jboss.modules.ModuleLoadError: java.se > at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) > at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608) > at org.jboss.modules.Module.loadModuleClass(Module.java:726) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) > at org.jboss.modules.Module.loadModuleClass(Module.java:731) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80) > at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > &amp#27;[0mException in thread "main" org.jboss.modules.ModuleLoadError: java.se > at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) > at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608) > at org.jboss.modules.Module.loadModuleClass(Module.java:726) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) > at org.jboss.modules.Module.loadModuleClass(Module.java:731) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80) > at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > {code} > I'm labeling this a Task for now rather than a Bug because I suspect the problem may be in the test infrastructure. In particular I recommend having a look at anything that changed in the WF Core launcher module in the 9.0.0.Beta4 release. The mixed domain tests use DomainLifecycleUtil, which in turn uses launcher's DomainCommandBuilder. Those use java.lang.Process to start a legacy PC using the JDK 11 jvm on the CI server. So the PC process is completely separate from the test client or the master PC/HC/servers. No reason the old code should stop working with JDK 11 so I suspect something has changed with the launcher. > [~jamezp] [~ropalka] FYI -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (AG-120) Hibernate Transaction Integration

by Ariel Carrera (Jira)

Ariel Carrera created AG-120: -------------------------------- Summary: Hibernate Transaction Integration Key: AG-120 URL: https://issues.jboss.org/browse/AG-120 Project: Agroal Issue Type: Enhancement Reporter: Ariel Carrera Assignee: Luis Barreiro Using Agroal with transaction integration support cause connection leaks in Hibernate related Jira ticket: [hibernate-agroal jira ticket|https://hibernate.atlassian.net/browse/HHH-13474?atlOrigin=eyJpIjo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3485) Misleading failure-description for capabilities in domain

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-3485?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3485: ---------------------------------------- Assignee: (was: Brian Stansberry) > Misleading failure-description for capabilities in domain > --------------------------------------------------------- > > Key: WFCORE-3485 > URL: https://issues.jboss.org/browse/WFCORE-3485 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 3.0.10.Final > Reporter: Ondrej Lukas > Priority: Minor > > In case when configuration in domain.xml tries to reference any capability from host.xml (or vice versa), but should not be able to reference it then it correctly fails, but there is failure-description which is misleading. > Start domain with default domain.xml and host.xml and run following CLI command and see: > {code} > /profile=full/subsystem=elytron/http-authentication-factory=some-factory:add(http-server-mechanism-factory=global,security-domain=ManagementDomain) > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.security-domain.ManagementDomain in context 'profile=full'; Possible registration points for this capability: > /host=master/subsystem=elytron/security-domain=* > /profile=*/subsystem=elytron/security-domain=*"}, > "rolled-back" => true > } > {code} > It should show only correct registration point {{/profile=\*/subsystem=elytron/security-domain=\*}}. It is misleading because ManagementDomain capability exists in {{/host=master/subsystem=elytron/security-domain=*}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12285) Use ModelNode.TRUE, ModelNode.FALSE, ModelNode.ZERO and ModelNode.ZERO_LONG

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12285: --------------------------------------- Summary: Use ModelNode.TRUE, ModelNode.FALSE, ModelNode.ZERO and ModelNode.ZERO_LONG Key: WFLY-12285 URL: https://issues.jboss.org/browse/WFLY-12285 Project: WildFly Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry ModelNode declares constants ModelNode.TRUE, ModelNode.FALSE, ModelNode.ZERO and ModelNode.ZERO_LONG. Save memory and a bit of runtime cost by using these instead of the hundreds of 'new ModelNode(true)' etc. This kind of thing does the trick for me: find ~/dev/wildfly/wildfly -type f -name "*.java" -exec grep -i "new ModelNode(false)" -l {} \; -exec sed -i "" 's/new ModelNode(false)/ModelNode.FALSE/g' {} \; -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019