June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11388) User is not informed about incorrect values in exposed-subsystems for MP Metrics

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11388?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-11388: ------------------------------- Priority: Major (was: Critical) > User is not informed about incorrect values in exposed-subsystems for MP Metrics > -------------------------------------------------------------------------------- > > Key: WFLY-11388 > URL: https://issues.jboss.org/browse/WFLY-11388 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Rostislav Svoboda > Assignee: Lin Gao > Priority: Major > > User is not informed about incorrect values in exposed-subsystems for MP Metrics > When I do stuff like > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch_jberet"]) > {code} > instead of > {code} > /subsystem=microprofile-metrics-smallrye/:write-attribute(name=exposed-subsystems, value=["batch-jberet"]) > {code} > I get no warning about non-existing subsystem. > User should be informed about misconfiguration. > Question is when: > - when server boots > - when the cli / management command is invoked > - both cases -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Jiří Locker (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Jiří Locker commented on DROOLS-1540: ------------------------------------- In which Drools version is this released? The Fixed version field is not set. > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1540) Drools does not work with spring-boot-devtools

by Jiří Locker (Jira)

[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Jiří Locker edited comment on DROOLS-1540 at 6/5/19 5:41 AM: ------------------------------------------------------------- In which Drools version is this released? The Fix Version field is not set. was (Author: jlocker): In which Drools version is this released? The Fixed version field is not set. > Drools does not work with spring-boot-devtools > ---------------------------------------------- > > Key: DROOLS-1540 > URL: https://issues.jboss.org/browse/DROOLS-1540 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.20.0.Final > Reporter: G Xiong > Assignee: Mario Fusco > Priority: Critical > Attachments: complete.zip > > > Drools does work with spring-boot-devtools. > If you add in pom.xml the following, no rules will be fired in Drools. > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-devtools</artifactId> > </dependency> > if you comment out this, then rules will be fired in Drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12167) Memory leak in metrics in standalone-ha configuration

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12167?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-12167: ------------------------------------ [~bsx303] could you please provide a head dump? If the issue occurs only with the HA configuration that means that one of the subsystems present only in that configuration is holding memory to store its metrics leading to the memory leak. > Memory leak in metrics in standalone-ha configuration > ----------------------------------------------------- > > Key: WFLY-12167 > URL: https://issues.jboss.org/browse/WFLY-12167 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 16.0.0.Final > Reporter: Bernd Stolle > Assignee: Jeff Mesnil > Priority: Major > Labels: memoryleak > > When started in standalone HA configuration every request to the recently added metrics endpoint ({{<management-if>:9990/metrics}}) lead to an increase in memory consumption until the JVM is slowed down significantly by GC to a point where even the requests to {{/health}} fail within a reasonable timeout (2s) and untlimately lead to OOM. > The same issue does not occur when WildFly is started in the default standalone configuration (non HA). > I can provide a (compressed) heap dump if required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-771) Analyze PRT Failure

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-771?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-771. --------------------------------- Resolution: Done Fixed worked, closing > Analyze PRT Failure > ------------------- > > Key: SWSQE-771 > URL: https://issues.jboss.org/browse/SWSQE-771 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Analyze the strange timeout error happening on PRT job: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/kiali-core-pr-e... > HTTPSConnectionPool(host='jenkins2.bc.jonqe.lab.eng.bos.redhat.com', port=8443): Max retries exceeded with url: /job/kiali-core-pr-e2e-test/api/python?tree=allBuilds%5Bnumber%2Curl%5D (Caused by ReadTimeoutError("HTTPSConnectionPool(host='jenkins2.bc.jonqe.lab.eng.bos.redhat.com', port=8443): Read timed out. (read timeout=10)",)) > PRT Failed, Please Contact QE -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4128) [DMN Designer] Unable to use a Decision Service that references imported elements

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4128?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-4128: ---------------------------------------- imho it should always be the case there is only 1 unique DMN model having that namespace (.../_5c8b9296-...), the drools:modelName extension could help to disambiguate, but this is going a bit beyond the spec. I believe once located, nothing prevents the WB tooling and in fact I would encourage, to then set the locationURI once resolved. my2c > [DMN Designer] Unable to use a Decision Service that references imported elements > --------------------------------------------------------------------------------- > > Key: DROOLS-4128 > URL: https://issues.jboss.org/browse/DROOLS-4128 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Loan info.dmn, Recommended Loan Products v3 no test case.dmn > > > The [attached|https://issues.jboss.org/secure/attachment/12451671/Recommended%...] DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4128) [DMN Designer] Unable to use a Decision Service that references imported elements

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4128?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4128: ----------------------------------- Attachment: Loan info.dmn Recommended Loan Products v3 no test case.dmn > [DMN Designer] Unable to use a Decision Service that references imported elements > --------------------------------------------------------------------------------- > > Key: DROOLS-4128 > URL: https://issues.jboss.org/browse/DROOLS-4128 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Loan info.dmn, Recommended Loan Products v3 no test case.dmn > > > The attached DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4128) [DMN Designer] Unable to use a Decision Service that references imported elements

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4128?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4128: ----------------------------------- Description: The [attached|https://issues.jboss.org/secure/attachment/12451671/Recommended%...] DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements. (was: The attached DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements.) > [DMN Designer] Unable to use a Decision Service that references imported elements > --------------------------------------------------------------------------------- > > Key: DROOLS-4128 > URL: https://issues.jboss.org/browse/DROOLS-4128 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Loan info.dmn, Recommended Loan Products v3 no test case.dmn > > > The [attached|https://issues.jboss.org/secure/attachment/12451671/Recommended%...] DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4128) [DMN Designer] Unable to use a Decision Service that references imported elements

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4128: -------------------------------------- Summary: [DMN Designer] Unable to use a Decision Service that references imported elements Key: DROOLS-4128 URL: https://issues.jboss.org/browse/DROOLS-4128 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.23.0.Final Reporter: Michael Anstis Assignee: Guilherme Gomes The attached DMN file has a Decision Service ("Whole Model Decision Service") that references imported items. This file fails to open in our editor as our {{DMNMarshaller}} does not handle resolution of imported elements in handling of {{DecisionService}} elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition

by Stefan Gr (Jira)

[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ] Stefan Gr commented on WFLY-11601: ---------------------------------- I had no time to investigate it myself but why is the {{BeanDeploymentModules.processBeanDeployments}} executed after the cleanup code? I've found this section in some [core documentation|https://github.com/weld/core/blob/603f95ab2a60bfbe962c4ec6c...] which does not make sense to me, when weld/CDI is not even know all beans. {noformat} You must ensure that WeldInitialListener.contextInitialized() is called after beans are deployed is complete (Bootstrap.deployBeans() has been called). {noformat} But if it may break existing code if we move out that part, there might be another solution that requires changes in the CDI implementation: * Set a flag which tells whether {{endInitialization was run}} * In {{contextInitialized}} we check this flag and if it is true, we simply fire the event for {{@ApplicationScoped}} * If the flag is false, we catch the ServletContext and fire the event as soon as {{endInitialization}} completes - just like it is done for non-web modules. That requires some thread-safe code but should not break any code. The performance overhead shouln't be noticable because this only affects the initialization and not the runtime. What do you think? Is there something I'm missing again? Does it require a spec change? > Weld vs Undertow bootstrap: Race condition > ------------------------------------------ > > Key: WFLY-11601 > URL: https://issues.jboss.org/browse/WFLY-11601 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Affects Versions: 15.0.1.Final > Reporter: Stefan Gr > Assignee: Matěj Novotný > Priority: Major > Attachments: TestApp.zip, TestLib.zip, changes.diff, deploy-failed.txt, deploy-mixed-success.txt, deploy-success.txt, test-app-1.0.0.war, weld-core-impl-3.0.5.Final.jar, weld-core-impl-3.0.5.Final.jar > > > WFLY-9732 / WFLY-10784 moves the completion of WELD from the WeldStartService to WeldStartCompetionService. This causes a race condition with the UndertowDeploymentService which executes the servlet listeners for context-initialized which again fires ApplicationScope-initialized events in CDI. > You can find more in [WELD-2557|https://issues.jboss.org/browse/WELD-2557?focusedCommentId=1368...]. > In short: WeldStartCompletionService and UndertowDeploymentService pushes the logic to the executor service. It may happen, that the logik of undertow runs before the weld completion. Events fired in the servlet listeners won't find all event observers. > A possible solution would bo to set the WeldStartCompletionService as a dependency of the UndertowDeploymentService -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019