December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12835) HealthChecks in subdeployments are not registered

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-12835: ------------------------------------ [~rsvoboda] I disagree. I specifically mention in the dev analysis that EAR deployment / multiple deployment is not supported in https://github.com/wildfly/wildfly-proposals/pull/259/files#diff-21f8d6fe.... > HealthChecks in subdeployments are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.redhat.com/browse/WFLY-12835 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > > After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. > EAR contains one WAR and one JAR. Both of them contains HealthChecks. > Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4878) Test Scenario: fix support for default stateless kieSession

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4878: ------------------------------------- Summary: Test Scenario: fix support for default stateless kieSession Key: DROOLS-4878 URL: https://issues.redhat.com/browse/DROOLS-4878 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca How to reproduce: - edit kmodule.xml and create only a default stateless session {code:java} <kmodule xmlns="http://www.drools.org/xsd/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <kbase name="myKieBase"> <ksession name="mySession" type="stateless" default="true"/> </kbase> </kmodule> {code} - create a Rule test scenario and specify in Setting panel {{stateless}} - run -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4778) Legacy LDAP realm, runtime operations and access to runtime attributes fail

by Ondrej Kotek (Jira)

[ https://issues.redhat.com/browse/WFCORE-4778?page=com.atlassian.jira.plug... ] Ondrej Kotek moved JBEAP-18359 to WFCORE-4778: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4778 (was: JBEAP-18359) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 10.0.0.Final (was: 7.3.0.GA) QE Test Coverage: (was: +) > Legacy LDAP realm, runtime operations and access to runtime attributes fail > --------------------------------------------------------------------------- > > Key: WFCORE-4778 > URL: https://issues.redhat.com/browse/WFCORE-4778 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Priority: Blocker > Labels: caching, ldap, legacy > > Runtime operations and access to runtime attributes fail for legacy LDAP realm. > {noformat} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("core-service" => "management"), > ("security-realm" => "authn-by-search-time-neg-neg"), > ("authentication" => "ldap"), > ("cache" => "by-search-time") > ]): java.lang.UnsupportedOperationException > at org.jboss.msc.service.ServiceControllerImpl.awaitValue(ServiceControllerImpl.java:1115) > at org.jboss.msc.service.DelegatingServiceController.awaitValue(DelegatingServiceController.java:110) > at org.jboss.as.domain.management.security.LdapCacheResourceDefinition$BaseRuntimeOpHandler.lookupService(LdapCacheResourceDefinition.java:321) > at org.jboss.as.domain.management.security.LdapCacheResourceDefinition$BaseRuntimeOpHandler.readAttribute(LdapCacheResourceDefinition.java:288) > at org.jboss.as.domain.management.security.LdapCacheResourceDefinition$BaseRuntimeOpHandler$1.execute(LdapCacheResourceDefinition.java:269) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4871) Complex value list doesn't work in guided rule editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4871?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4871: -------------------------------- Release Notes Text: (was: Users of guided rule editor are unable to design "is contained in comma separated list" constraint in combination with complex values. Complex values are those containing a comma inside or they are wrapped by brackets.) > Complex value list doesn't work in guided rule editor > ----------------------------------------------------- > > Key: DROOLS-4871 > URL: https://issues.redhat.com/browse/DROOLS-4871 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This issue was found during RHPAM-2323 review. It is slightly different however related. > The issue can be spotted on multiple places: > - Guided Rule > - Guided Rule Template > - Guided Decision Table - BRL condition fragment > If user wants to define constraint with operator *is contained in ([list of values])* then there is issue if the *[list of values]* is complex - it contains additional quotes or brackets. > h2. Reproducer Test > https://github.com/kiegroup/drools/pull/2588 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4871) Complex value list doesn't work in guided rule editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4871?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4871: -------------------------------- Affects: (was: Release Notes) > Complex value list doesn't work in guided rule editor > ----------------------------------------------------- > > Key: DROOLS-4871 > URL: https://issues.redhat.com/browse/DROOLS-4871 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > This issue was found during RHPAM-2323 review. It is slightly different however related. > The issue can be spotted on multiple places: > - Guided Rule > - Guided Rule Template > - Guided Decision Table - BRL condition fragment > If user wants to define constraint with operator *is contained in ([list of values])* then there is issue if the *[list of values]* is complex - it contains additional quotes or brackets. > h2. Reproducer Test > https://github.com/kiegroup/drools/pull/2588 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4775) Some .CLI commands that has been working since WF9 fails on WF18

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4775?page=com.atlassian.jira.plug... ] Jeff Mesnil resolved WFCORE-4775. --------------------------------- Fix Version/s: 11.0.0.Beta5 Resolution: Done With WFCORE-4774 in, the reproducer no longer throws a StackOverflowError {code} [standalone@localhost:9990 /] /subsystem=transactions:write-attribute(name=node-identifier,value=ismobile) { "outcome" => "success", "response-headers" => { "operation-requires-restart" => true, "process-state" => "restart-required" } } [standalone@localhost:9990 /] /subsystem=undertow:write-attribute(name=statistics-enabled,value=true) { "outcome" => "success", "response-headers" => {"process-state" => "restart-required"} } {code} > Some .CLI commands that has been working since WF9 fails on WF18 > ---------------------------------------------------------------- > > Key: WFCORE-4775 > URL: https://issues.redhat.com/browse/WFCORE-4775 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 11.0.0.Beta4 > Reporter: Peter Jonsson > Assignee: Yeray Borges > Priority: Critical > Fix For: 11.0.0.Beta5 > > > Error message is > ERROR [org.jboss.as.cli.CommandContext] (CLI command) { > "outcome" => "failed", > "failure-description" => "java.lang.StackOverflowError:null" > } > And in the log > 2019-10-21 19:14:44,377 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0403: Unexpected failure during execution of the following operation(s): [{ > "address" => [("subsystem" => "undertow")], > "operation" => "write-attribute", > "name" => "statistics-enabled", > "value" => true, > "operation-headers" => { > "caller-type" => "user", > "access-mechanism" => "NATIVE" > } > }]: java.lang.StackOverflowError > at org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:418) > at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392) > at org.jboss.as.controller.CapabilityRegistry.getDependentCapabilityStatus(CapabilityRegistry.java:426) > at org.jboss.as.controller.CapabilityRegistry.getCapabilityStatus(CapabilityRegistry.java:392) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4689) [DMN Designer] Code Completion - Setup Monaco (loader)

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4689?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4689: -------------------------------- Attachment: firefox.webm > [DMN Designer] Code Completion - Setup Monaco (loader) > ------------------------------------------------------ > > Key: DROOLS-4689 > URL: https://issues.redhat.com/browse/DROOLS-4689 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: auto-vs-explicit.webm, completion-twice.webm, completions-tabulator.webm, context-completions.webm, firefox.webm, last-entry-completion.webm > > > Setup Monaco library (and it's loader) into the DMN webapp. > ⚠️ Notice: test it in all environments (dev-webapp, VSCode webapp, Business Central webapp) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4877) Upgrade ECJ to make it Java 11 compatible

by Marek Novotny (Jira)

[ https://issues.redhat.com/browse/DROOLS-4877?page=com.atlassian.jira.plug... ] Marek Novotny updated DROOLS-4877: ---------------------------------- Labels: java11 (was: ) > Upgrade ECJ to make it Java 11 compatible > ----------------------------------------- > > Key: DROOLS-4877 > URL: https://issues.redhat.com/browse/DROOLS-4877 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: java11 > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4877) Upgrade ECJ to make it Java 11 compatible

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4877: ----------------------------------- Summary: Upgrade ECJ to make it Java 11 compatible Key: DROOLS-4877 URL: https://issues.redhat.com/browse/DROOLS-4877 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4645) High memory consumption with JIT

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4645?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4645: -------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > High memory consumption with JIT > -------------------------------- > > Key: DROOLS-4645 > URL: https://issues.redhat.com/browse/DROOLS-4645 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.29.0.Final > Reporter: Radovan Synek > Assignee: Mario Fusco > Priority: Critical > Attachments: Screenshot from 2019-10-15 10-30-27.png, Screenshot from 2019-10-15 10-31-53.png > > > Employee Rostering example for OptaPlanner shows excessive memory consumption, which is connected with Drools score calculation. > Please see the reproducer - running it without drools JIT finishes on time with 3GB of memory while with drools JIT being active it fails due to "GC overhead limit exceeded" despite the fact it god twice as much memory. > Logging (add -Dlogback.level.org.optaplanner=trace to the execute_jit.sh script) showed there is a huge pillar move changing ~hundreds of entities which takes seconds to calculate score. During this move's evaluation, the memory consumption increases to a point when GC takes over and later fails. > Memory sampling and heap dump investigation showed there are ~10^7 objects of org.drools.core.reteoo.FromNodeLeftTuple class, taking more memory than any other data type in the VM. > See the attached screenshots. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019