January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ] Jozef Marko resolved DROOLS-4949. --------------------------------- Resolution: Done > Blue rectangle above test scenario collection editor > ---------------------------------------------------- > > Key: DROOLS-4949 > URL: https://issues.redhat.com/browse/DROOLS-4949 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13000?page=com.atlassian.jira.plugi... ] Dominik Derwiński commented on WFLY-13000: ------------------------------------------ Perhaps jaxrs / resteasy module should pull by default only smallest possible subset of libraries, with all others being optional for the user to add. It's not easy to exclude implicit dependencies (and one is generally not aware of the problem until the app is deployed). > Put an end to problems with Jackson caused by jaxrs subsystem > ------------------------------------------------------------- > > Key: WFLY-13000 > URL: https://issues.redhat.com/browse/WFLY-13000 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 18.0.1.Final > Reporter: Dominik Derwiński > Assignee: Alessio Soldano > Priority: Major > > There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: > {noformat} > java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' > {noformat} > or > {noformat} > java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) > {noformat} > Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Found these on the net while trying to solve my issue: > http://alloutfornoloss.com/exclude-jackson-module-wildfly/ > https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... > https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... > https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... > https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... > https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... > https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s > https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4927: -------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4927: ----------------------------------- Assignee: Mario Fusco (was: Luca Molteni) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4746: -------------------------------------- Sprint: (was: 2020 Week 04-06 (from Jan 20)) > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4949: -------------------------------- > Blue rectangle above test scenario collection editor > ---------------------------------------------------- > > Key: DROOLS-4949 > URL: https://issues.redhat.com/browse/DROOLS-4949 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4699) Supporting long value input

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4699?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4699: ------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28)) > Supporting long value input > --------------------------- > > Key: DROOLS-4699 > URL: https://issues.redhat.com/browse/DROOLS-4699 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Description here: > https://issues.jboss.org/browse/DROOLS-4574?focusedCommentId=13794570&pag... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12952) MP Health returns UP when checks are expected but not installed yet.

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12952?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-12952: ------------------------------- Priority: Critical (was: Blocker) > MP Health returns UP when checks are expected but not installed yet. > -------------------------------------------------------------------- > > Key: WFLY-12952 > URL: https://issues.redhat.com/browse/WFLY-12952 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 18.0.0.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > MicroProfile Health 2.0 specification [link|https://github.com/eclipse/microprofile-health/blob/2.0/spec/src/mai...] says: > * A producer MUST support custom, application level health check procedures > * A producer SHOULD support reasonable out-of-the-box procedures > * A producer with no health check procedures expected or installed MUST return positive overall status (i.e. HTTP 200) > * A producer with health check procedures expected but not yet installed MUST return negative overall status (i.e. HTTP 503) > When I deploy and application with a readiness probe before WildFly is started, from my and namely OpenShift POV the health check procedure is expected from the very beginning. > _Let me note that on OpenShift starting the served should mean starting the service._ > Hence I expect negative overall status till the probe is ready and is able to provide response. > However WildFly with default setting responses with status UP: > {code:bash} > while true; do echo $(date +"%T.%3N") ; curl localhost:9990/health/ready; echo ""; done > 17:17:56.438 curl: (7) Failed to connect to localhost port 9990: Connection refused > 17:17:56.452 curl: (7) Failed to connect to localhost port 9990: Connection refused > 17:17:56.466 {"status":"UP","checks":[]} > ... > 17:18:01.121 {"status":"UP","checks":[]} > 17:18:01.133 {"status":"DOWN","checks":[{"name":"delayed-readiness","status":"DOWN"}]} > {code} > This violates (4) bullet in the specification. > WildFly provides option to set global Status when probes are not defined ([documentation|https://doc-stage.usersys.redhat.com/documentation/en-us/re...]) > Which would mean the scenario would behave according to the specification. Yet the default state violates it. > If the default value were _DOWN_ we would run into an issue if WildFly without deployment were used (for example as backup for AMQ). The status would be just DOWN: > {noformat} > 17:22:41.719 > {"status":"DOWN","checks":[]} > {noformat} > And that would violate (3) in the specification. > TCK tests do not cover the scenario well. > Is there a way to return _DOWN_ until WildFly scan a deployment and if no health check is found (thus not expected) then start to return _UP_ ? The scan should happen during MP Health initialization. > If there is no deployment, the _UP_ it is. > Setting the priority to blocker since WildFly 19 shall be EAP 7.3.0.CD19 which is supposed to run on OpenShift. With this behavior health check is not very useful because: > * OpenShift starts the service wait some time and start asking for health status > * WildFly responses _UP_ yet application helathcheck is not installed yet > * With health status _UP_ OpenShift consider a pod ready > * In this point application is installed, health status is _DOWN_ (a DB is down) however OpenShift flow is somewhere else -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Edson Tirelli commented on DROOLS-4778: --------------------------------------- [~manstis] I agree. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1051) Prepare document for OCP layered testing

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1051?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1051. ---------------------------------- Resolution: Done > Prepare document for OCP layered testing > ---------------------------------------- > > Key: SWSQE-1051 > URL: https://issues.redhat.com/browse/SWSQE-1051 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We need to describe how and what will be tested during different ocp milestones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 January 2020