April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1124) Automate filters by 2 names

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1124?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1124. ----------------------------------- Resolution: Done > Automate filters by 2 names > --------------------------- > > Key: SWSQE-1124 > URL: https://issues.redhat.com/browse/SWSQE-1124 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://issues.redhat.com/browse/OSSM-93 > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13390) :migrate operation on legacy messaging subsystem fails with 7.4.0.CD19 (WF19)

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13390?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet moved JBEAP-19278 to WFLY-13390: -------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13390 (was: JBEAP-19278) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS Migration (was: JMS) (was: Migration) Affects Version/s: 19.0.0.Final (was: 7.4.0.CD19) > :migrate operation on legacy messaging subsystem fails with 7.4.0.CD19 (WF19) > ----------------------------------------------------------------------------- > > Key: WFLY-13390 > URL: https://issues.redhat.com/browse/WFLY-13390 > Project: WildFly > Issue Type: Bug > Components: JMS, Migration > Affects Versions: 19.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Critical > > CD19 (WF19) introduces several failures in tests running the {{:migrate}} operation on legacy configuration files. > See [^standalone-full-ha-migrate.xml.original] for configuration file which is subject of migration. > {code} > ... > <broadcast-groups> > <broadcast-group name="groupS"> > <socket-binding>messaging-group</socket-binding> > </broadcast-group> > ... > </broadcast-groups> > ... > {code} > See [^standalone-full-ha-migrate.xml.migrated] for configuration file after migration using 7.3.0 EAP. > {code} > ... > <broadcast-group socket-binding="messaging-group" name="groupS"/> > ... > {code} > Migration outcome with 7.4.0.CD19.CR1 (WF19) > {code} > { > "outcome" : "failed", > "result" : { > "migration-warnings" : [], > "migration-error" : { > "operation" : { > "socket-binding" : "messaging-group", > "connectors" : null, > "operation" : "add", > "address" : [ > { > "subsystem" : "messaging-activemq" > }, > { > "server" : "default" > }, > { > "broadcast-group" : "groupS" > } > ], > "operation-headers" : { > "caller-type" : "user", > "access-mechanism" : "NATIVE" > } > }, > "result" : { > "outcome" : "failed", > "failure-description" : "WFLYCTL0155: 'connectors' may not be null", > "rolled-back" : true > } > } > }, > "failure-description" : "WFLYMSG0081: Migration failed, see results for more details.", > "rolled-back" : true > } > {code} > Unfortunately I do not have a deeper knowledge of messaging subsystem to be able to tell what should be the best outcome of migration here. > Could be related to https://issues.redhat.com/browse/WFLY-10339 Broadcast/discovery-group resources have ambiguous requirement specs > *Steps to reproduce* > {code} > $ cp standalone-full-ha-migrate.xml.original jboss-eap-7.4/standalone/configuration/standalone.xml > $ ./jboss-eap-7.4/bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server --admin-only=true > [standalone@embedded /] /subsystem=messaging:migrate > { > "outcome" => "failed", > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13390) :migrate operation on legacy messaging subsystem fails with WF19

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13390?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13390: ------------------------------------- Summary: :migrate operation on legacy messaging subsystem fails with WF19 (was: :migrate operation on legacy messaging subsystem fails with 7.4.0.CD19 (WF19)) > :migrate operation on legacy messaging subsystem fails with WF19 > ---------------------------------------------------------------- > > Key: WFLY-13390 > URL: https://issues.redhat.com/browse/WFLY-13390 > Project: WildFly > Issue Type: Bug > Components: JMS, Migration > Affects Versions: 19.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Critical > > CD19 (WF19) introduces several failures in tests running the {{:migrate}} operation on legacy configuration files. > See [^standalone-full-ha-migrate.xml.original] for configuration file which is subject of migration. > {code} > ... > <broadcast-groups> > <broadcast-group name="groupS"> > <socket-binding>messaging-group</socket-binding> > </broadcast-group> > ... > </broadcast-groups> > ... > {code} > See [^standalone-full-ha-migrate.xml.migrated] for configuration file after migration using 7.3.0 EAP. > {code} > ... > <broadcast-group socket-binding="messaging-group" name="groupS"/> > ... > {code} > Migration outcome with 7.4.0.CD19.CR1 (WF19) > {code} > { > "outcome" : "failed", > "result" : { > "migration-warnings" : [], > "migration-error" : { > "operation" : { > "socket-binding" : "messaging-group", > "connectors" : null, > "operation" : "add", > "address" : [ > { > "subsystem" : "messaging-activemq" > }, > { > "server" : "default" > }, > { > "broadcast-group" : "groupS" > } > ], > "operation-headers" : { > "caller-type" : "user", > "access-mechanism" : "NATIVE" > } > }, > "result" : { > "outcome" : "failed", > "failure-description" : "WFLYCTL0155: 'connectors' may not be null", > "rolled-back" : true > } > } > }, > "failure-description" : "WFLYMSG0081: Migration failed, see results for more details.", > "rolled-back" : true > } > {code} > Unfortunately I do not have a deeper knowledge of messaging subsystem to be able to tell what should be the best outcome of migration here. > Could be related to https://issues.redhat.com/browse/WFLY-10339 Broadcast/discovery-group resources have ambiguous requirement specs > *Steps to reproduce* > {code} > $ cp standalone-full-ha-migrate.xml.original jboss-eap-7.4/standalone/configuration/standalone.xml > $ ./jboss-eap-7.4/bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server --admin-only=true > [standalone@embedded /] /subsystem=messaging:migrate > { > "outcome" => "failed", > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1123) 3Scale tests backport to 1.1

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1123?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan closed SWSQE-1123. --------------------------------- Resolution: Done already done > 3Scale tests backport to 1.1 > ---------------------------- > > Key: SWSQE-1123 > URL: https://issues.redhat.com/browse/SWSQE-1123 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1125) Update job parameters for jaeger

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1125: ------------------------------------ Summary: Update job parameters for jaeger Key: SWSQE-1125 URL: https://issues.redhat.com/browse/SWSQE-1125 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We are still using parameters for jaeger like: JAEGER_OPERATOR_HUB=quay.io/maistra JAEGER_OPERATOR_IMAGE=jaeger-rhel7-operator JAEGER_OPERATOR_TAG=latest-qe JAEGER_HUB=quay.io/maistra JAEGER_TAG=latest-qe We need to make it optional as it's not necessary when using OLM. Remember to update default values and PR jobs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1124) Automate filters by 2 names

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1124?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan closed SWSQE-1124. --------------------------------- Resolution: Rejected > Automate filters by 2 names > --------------------------- > > Key: SWSQE-1124 > URL: https://issues.redhat.com/browse/SWSQE-1124 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://issues.redhat.com/browse/OSSM-93 > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1124) Automate filters by 2 names

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1124?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reopened SWSQE-1124: ----------------------------------- > Automate filters by 2 names > --------------------------- > > Key: SWSQE-1124 > URL: https://issues.redhat.com/browse/SWSQE-1124 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://issues.redhat.com/browse/OSSM-93 > https://polarion.engineering.redhat.com/polarion/#/project/SwiftSunshine/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5061) DMN codegen DMNContext and DMNResult

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5061?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5061: ----------------------------------- Description: A codegen facility is required to generate statically code strongly typed for the input/output of a DMN model, considering also the data types defined inside the DMN model as ItemDefinition. Surface and interface common to: * BPMN integration: when invoking DMN from BPMN, the return of the evaluation is a Map and not the domain model * Kogito/OpenAPI/Swagger: when using the codegenerated version, annotation shall explain the swagger API the expected input/output type of the REST request for DMN ** for Quarkus based, use RegisterForReflection annotation ** use MP validation for allowedvalues * DMN Editor: when importing a Java Class in the editor, it shall use the user-supplied Java Class was: A codegen facility is required to generate statically code strongly typed for the input/output of a DMN model, considering also the data types defined inside the DMN model as ItemDefinition. Surface and interface common to: * BPMN integration: when invoking DMN from BPMN, the return of the evaluation is a Map and not the domain model * Kogito/OpenAPI/Swagger: when using the codegenerated version, annotation shall explain the swagger API the expected input/output type of the REST request for DMN * DMN Editor: when importing a Java Class in the editor, it shall use the user-supplied Java Class > DMN codegen DMNContext and DMNResult > ------------------------------------ > > Key: DROOLS-5061 > URL: https://issues.redhat.com/browse/DROOLS-5061 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > A codegen facility is required to generate statically code strongly typed for the input/output of a DMN model, considering also the data types defined inside the DMN model as ItemDefinition. > Surface and interface common to: > * BPMN integration: when invoking DMN from BPMN, the return of the evaluation is a Map and not the domain model > * Kogito/OpenAPI/Swagger: when using the codegenerated version, annotation shall explain the swagger API the expected input/output type of the REST request for DMN > ** for Quarkus based, use RegisterForReflection annotation > ** use MP validation for allowedvalues > * DMN Editor: when importing a Java Class in the editor, it shall use the user-supplied Java Class -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4860) Performance degradation with the LogContextSelector on Java 11

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4860?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-4860: ---------------------------------- Labels: downstream_dependency (was: ) > Performance degradation with the LogContextSelector on Java 11 > --------------------------------------------------------------- > > Key: WFCORE-4860 > URL: https://issues.redhat.com/browse/WFCORE-4860 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > Fix For: 12.0.0.Beta1 > > > As described in LOGMGR-263 there is a performance impact on Java 11 when using the {{ClassLoaderLogContextSelector}}. In WildFly for users that do not use per-deployment logging we could get around this by not using that log context selector. This would not fix the performance impact for users using Java 11 and per-deployment logging however. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13273) Create tests for WFCORE-4860

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13273?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-13273: --------------------------------- Labels: downstream_dependency (was: ) > Create tests for WFCORE-4860 > ---------------------------- > > Key: WFLY-13273 > URL: https://issues.redhat.com/browse/WFLY-13273 > Project: WildFly > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > > WFCORE-4860 makes some change in behavior for how the log context selector works. This is to help with some performance issues with Java 9+. The tests need to live in WildFly as we need multiple deployments and EAR's which the core test suite cannot handle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020