November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4828) [DMN Designer] The tab in Data Type constraints while adding Enumeration goes to wrong icon

by Daniel José dos Santos (Jira)

Daniel José dos Santos created DROOLS-4828: ---------------------------------------------- Summary: [DMN Designer] The tab in Data Type constraints while adding Enumeration goes to wrong icon Key: DROOLS-4828 URL: https://issues.jboss.org/browse/DROOLS-4828 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Daniel José dos Santos Assignee: Michael Anstis 1. In the Data Type constraints modal, when adding "Enumeration", after the string is typed if user press "Tab" the focus goes to the cancel button (the X) instead of the "V" button (the apply). 2. I think is not clear how to apply with keyboard shortcut. In the Data Type tab, CTRL + S saves, but in this modal CTRL + S calls the default browser behavior. I think it have to be consistent. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

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

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-12835?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-12835: ------------------------------- Description: 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... was: After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. Test source: https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic... > HealthChecks in subdeploymnets are not registered > ------------------------------------------------- > > Key: WFLY-12835 > URL: https://issues.jboss.org/browse/WFLY-12835 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 18.0.1.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > 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)

5 years, 10 months

1
0
0 / 0

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

by Ivan Straka (Jira)

Ivan Straka created WFLY-12835: ---------------------------------- Summary: HealthChecks in subdeploymnets are not registered Key: WFLY-12835 URL: https://issues.jboss.org/browse/WFLY-12835 Project: WildFly Issue Type: Bug Components: MP Health Affects Versions: 18.0.1.Final Reporter: Ivan Straka Assignee: Jeff Mesnil After EAR is deployed HealthChecks are not registered and not exposed under _/health_ endpoint. 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)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4827) Refactoring Test Tool data population

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4827?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4827: ------------------------------- Summary: Refactoring Test Tool data population (was: Refactor Test Tool data population) > Refactoring Test Tool data population > ------------------------------------- > > Key: DROOLS-4827 > URL: https://issues.jboss.org/browse/DROOLS-4827 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: TestScenario > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4827) Refactor Test Tool data population

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4827?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4827: ------------------------------- Summary: Refactor Test Tool data population (was: Refactort Test Tool data population) > Refactor Test Tool data population > ---------------------------------- > > Key: DROOLS-4827 > URL: https://issues.jboss.org/browse/DROOLS-4827 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: TestScenario > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-218) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka edited comment on WFWIP-218 at 11/29/19 10:12 AM: ------------------------------------------------------------------- Just mentioning that I started to investigate on this. I agree with [~tomekadamski] that the WFTC-75 seems to be fixing the WFTC-77 as well. I created the reproducer https://gitlab.mw.lab.eng.bos.redhat.com/ochaloup/tests-transactions/comm... that does the same (or I assume it does the same) as the test in the eap qe openshift testsuite. On debugging and testing all works fine. But! The strange thing is that this issue WFWIP-218 is reproducible with the test {{EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail}} and the scale down does clean the WFTC folder - the commit happens during the recovery, the Narayana object store is clean but the WFTC folder is not empty. I will be running more investigation on this. For sake of completeness I run this {code} mvn clean test -Pcd -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -Dconsole-log-level=DEBUG -Poperator {code} on local CRC instance (http://pastebin.test.redhat.com/815593) with {{test.properties}} {code} xtf.openshift.namespace=ochaloup-namespace xtf.bm.namespace=ochaloup-builds-namespace # this is the url of CRC, try `crc ip` xtf.openshift.url=https://192.168.130.11:6443 xtf.eap.properties.location=/opt/eap xtf.openshift.binary.path=/home/ochaloup/.crc/bin/oc # operator built by Jeff and published xtf.operator.wildfly.image=docker-registry.engineering.redhat.com/jbossqe... # for the latest EAP image to take xtf.eap.cd.image=registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-... xtf.eap.cd.properties.eap.runtime.image=registry-proxy.engineering.redhat... xtf.waiting.timeout=600000 test.script.debug=true # needed for yaml not being downloaded from quay repo or what xtf.operator.eap.resources.context= {code} was (Author: ochaloup): Just mentioning that I started to investigate on this. I agree with [~tomekadamski] that the WFTC-75 seems to be fixing the WFTC-77 as well. I created the reproducer https://gitlab.mw.lab.eng.bos.redhat.com/ochaloup/tests-transactions/comm... that does the same (or I assume it does the same) as the test in the eap qe openshift testsuite. On debugging and testing all works fine. But! The strange thing is that this issue WFWIP-218 is reproducible with the test `EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail` and the scale down does clean the WFTC folder - the commit happens during the recovery, the Narayana object store is clean but the WFTC folder is not empty. I will be running more investigation on this. For sake of completeness I run this {code} mvn clean test -Pcd -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -Dconsole-log-level=DEBUG -Poperator {code} on local CRC instance (http://pastebin.test.redhat.com/815593) with {{test.properties}} {code} xtf.openshift.namespace=ochaloup-namespace xtf.bm.namespace=ochaloup-builds-namespace # this is the url of CRC, try `crc ip` xtf.openshift.url=https://192.168.130.11:6443 xtf.eap.properties.location=/opt/eap xtf.openshift.binary.path=/home/ochaloup/.crc/bin/oc # operator built by Jeff and published xtf.operator.wildfly.image=docker-registry.engineering.redhat.com/jbossqe... # for the latest EAP image to take xtf.eap.cd.image=registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-... xtf.eap.cd.properties.eap.runtime.image=registry-proxy.engineering.redhat... xtf.waiting.timeout=600000 test.script.debug=true # needed for yaml not being downloaded from quay repo or what xtf.operator.eap.resources.context= {code} > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFWIP-218 > URL: https://issues.jboss.org/browse/WFWIP-218 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > this follows up on WFWIP-206 > While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful > Scenario: > *ejb client* (app tx-client, pod tx-client-0): > * EJB business method > ** lookup remote EJB > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > ** call remote EJB > *ejb server* (app tx-server, pod tx-server-0): > * EJB business method > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > *testTxStatelessServerSecondCommitThrowRmFail* > ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}} > Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client and transactions on client aren't commited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-218) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on WFWIP-218: ---------------------------------------- Just mentioning that I started to investigate on this. I agree with [~tomekadamski] that the WFTC-75 seems to be fixing the WFTC-77 as well. I created the reproducer https://gitlab.mw.lab.eng.bos.redhat.com/ochaloup/tests-transactions/comm... that does the same (or I assume it does the same) as the test in the eap qe openshift testsuite. On debugging and testing all works fine. But! The strange thing is that this issue WFWIP-218 is reproducible with the test `EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail` and the scale down does clean the WFTC folder - the commit happens during the recovery, the Narayana object store is clean but the WFTC folder is not empty. I will be running more investigation on this. For sake of completeness I run this {code} mvn clean test -Pcd -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -Dconsole-log-level=DEBUG -Poperator {code} on local CRC instance (http://pastebin.test.redhat.com/815593) with {{test.properties}} {code} xtf.openshift.namespace=ochaloup-namespace xtf.bm.namespace=ochaloup-builds-namespace # this is the url of CRC, try `crc ip` xtf.openshift.url=https://192.168.130.11:6443 xtf.eap.properties.location=/opt/eap xtf.openshift.binary.path=/home/ochaloup/.crc/bin/oc # operator built by Jeff and published xtf.operator.wildfly.image=docker-registry.engineering.redhat.com/jbossqe... # for the latest EAP image to take xtf.eap.cd.image=registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-... xtf.eap.cd.properties.eap.runtime.image=registry-proxy.engineering.redhat... xtf.waiting.timeout=600000 test.script.debug=true # needed for yaml not being downloaded from quay repo or what xtf.operator.eap.resources.context= {code} > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFWIP-218 > URL: https://issues.jboss.org/browse/WFWIP-218 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > this follows up on WFWIP-206 > While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful > Scenario: > *ejb client* (app tx-client, pod tx-client-0): > * EJB business method > ** lookup remote EJB > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > ** call remote EJB > *ejb server* (app tx-server, pod tx-server-0): > * EJB business method > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > *testTxStatelessServerSecondCommitThrowRmFail* > ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}} > Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client and transactions on client aren't commited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4827) Refactort Test Tool data population

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4827: ---------------------------------- Summary: Refactort Test Tool data population Key: DROOLS-4827 URL: https://issues.jboss.org/browse/DROOLS-4827 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing, Test Scenarios Editor Reporter: Yeser Amer Assignee: Yeser Amer -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4765) Remove licenses for artifacts that are not in the distribution

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4765: ----------------------------------- Summary: Remove licenses for artifacts that are not in the distribution Key: WFCORE-4765 URL: https://issues.jboss.org/browse/WFCORE-4765 Project: WildFly Core Issue Type: Bug Components: Build System Affects Versions: 11.0.0.Beta3 Reporter: Jeff Mesnil Assignee: Jeff Mesnil The following artifacts are not in the WildFly distribution and can be excluded from the wildfly-core feature-packs: * org.wildfly.core:wildfly-core-model-test-framework * Artifacts with group id org.wildfly.galleon-plugins * org.wildfly.security:wildfly-elytron -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1012) publish_jenkins_console is failing with RuntimeError: maximum recursion depth exceeded in cmp

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-1012?page=com.atlassian.jira.plugin... ] Filip Brychta resolved SWSQE-1012. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/publish-jenkins-console/pull/5 > publish_jenkins_console is failing with RuntimeError: maximum recursion depth exceeded in cmp > --------------------------------------------------------------------------------------------- > > Key: SWSQE-1012 > URL: https://issues.jboss.org/browse/SWSQE-1012 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > e.g. this jobs failed: > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/pr-jobs/job/py... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2019