December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1035) Wizard - TLS MUTUAL

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1035?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1035: ------------------------------------- Assignee: Hayk Hovsepyan > Wizard - TLS MUTUAL > ------------------- > > Key: SWSQE-1035 > URL: https://issues.redhat.com/browse/SWSQE-1035 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Client Certificate > Private Key -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12878) Addition of a multiversion testcase for WFLY-12871

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-12878?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos moved JBEAP-18313 to WFLY-12878: -------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12878 (was: JBEAP-18313) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Testing/Validation) > Addition of a multiversion testcase for WFLY-12871 > -------------------------------------------------- > > Key: WFLY-12878 > URL: https://issues.redhat.com/browse/WFLY-12878 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Addition of a multiversion testcase for WFLY-12871 in order to be tested in all the servers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-286) MP Fault Tolerance - Fault Tolerance is missing logging code when activated

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-286?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-286: -------------------------------------- This would require converting the whole project to use jboss-logging properly with IDs which is not viable in the current effort. > MP Fault Tolerance - Fault Tolerance is missing logging code when activated > --------------------------------------------------------------------------- > > Key: WFWIP-286 > URL: https://issues.redhat.com/browse/WFWIP-286 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Minor > > If MP FT is activated by deployment then INFO log is missing logging code: > {code} > 10:18:31,626 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated > {code} > Logging code should be added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-285) MP Fault Tolerance - Fault Tolerance is activated by deployment without MP FT

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-285?page=com.atlassian.jira.plugin... ] Radoslav Husar edited comment on WFWIP-285 at 12/12/19 7:06 AM: ---------------------------------------------------------------- Updated the PR with the fix. We had to leverage jandex to perform annotation processing. was (Author: rhusar): Updated the PR with the fix. We need to leverage jandex to do some annotation processing. > MP Fault Tolerance - Fault Tolerance is activated by deployment without MP FT > ----------------------------------------------------------------------------- > > Key: WFWIP-285 > URL: https://issues.redhat.com/browse/WFWIP-285 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > Once microprofile-fault-tolerance extension/subsystem is added then deployment wihtout MP FT activates it: > {code} > 16:40:40,525 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated > {code} > Actual Result: Deployment without MP Fault Tolerance activates MP FT. > Expected Result: Deployment without MP Fault Tolerance must not activate MP FT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-286) MP Fault Tolerance - Fault Tolerance is missing logging code when activated

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-286?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFWIP-286: --------------------------------- Priority: Minor (was: Major) > MP Fault Tolerance - Fault Tolerance is missing logging code when activated > --------------------------------------------------------------------------- > > Key: WFWIP-286 > URL: https://issues.redhat.com/browse/WFWIP-286 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Minor > > If MP FT is activated by deployment then INFO log is missing logging code: > {code} > 10:18:31,626 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated > {code} > Logging code should be added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-284: ---------------------------------------- No problem, thanks [~tterem] > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Tomas Terem (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Tomas Terem closed WFWIP-284. ----------------------------- > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-284) Clarify what is invalid header name

by Tomas Terem (Jira)

[ https://issues.redhat.com/browse/WFWIP-284?page=com.atlassian.jira.plugin... ] Tomas Terem commented on WFWIP-284: ----------------------------------- [~dlofthouse] Ok, you are right. I am closing this. Sorry for the confusion. > Clarify what is invalid header name > ----------------------------------- > > Key: WFWIP-284 > URL: https://issues.redhat.com/browse/WFWIP-284 > Project: WildFly WIP > Issue Type: Task > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Header names should follow rules described here: > https://tools.ietf.org/html/rfc5322#section-2.2 > However, rules for custom headers seems to be more restrictive - for example @ or = are not allowed. > I see that these characters are mentioned in https://tools.ietf.org/html/rfc2616#page-16, but it only says that they should be in quotes. However I am not able to configure header containing them in quotes either. > Is this on purpose? > If yes, this needs to be mentioned in analysis&documentation. If not, we need to create critical JBEAP jira for 7.4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-285) MP Fault Tolerance - Fault Tolerance is activated by deployment without MP FT

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-285?page=com.atlassian.jira.plugin... ] Radoslav Husar resolved WFWIP-285. ---------------------------------- Resolution: Done Updated the PR with the fix. We need to leverage jandex to do some annotation processing. > MP Fault Tolerance - Fault Tolerance is activated by deployment without MP FT > ----------------------------------------------------------------------------- > > Key: WFWIP-285 > URL: https://issues.redhat.com/browse/WFWIP-285 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > Once microprofile-fault-tolerance extension/subsystem is added then deployment wihtout MP FT activates it: > {code} > 16:40:40,525 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated > {code} > Actual Result: Deployment without MP Fault Tolerance activates MP FT. > Expected Result: Deployment without MP Fault Tolerance must not activate MP FT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1038) VS Overview - HTTP Route automate

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1038: ------------------------------------- Summary: VS Overview - HTTP Route automate Key: SWSQE-1038 URL: https://issues.redhat.com/browse/SWSQE-1038 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- 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