December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12839) Prepare test for allowing addition of HTTP headers to management console responses

by Tomas Terem (Jira)

Tomas Terem created WFLY-12839: ---------------------------------- Summary: Prepare test for allowing addition of HTTP headers to management console responses Key: WFLY-12839 URL: https://issues.jboss.org/browse/WFLY-12839 Project: WildFly Issue Type: Task Components: Management, Test Suite Reporter: Tomas Terem Assignee: Tomas Terem -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12839) Prepare tests for allowing addition of HTTP headers to management console responses

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFLY-12839?page=com.atlassian.jira.plugin... ] Tomas Terem updated WFLY-12839: ------------------------------- Summary: Prepare tests for allowing addition of HTTP headers to management console responses (was: Prepare test for allowing addition of HTTP headers to management console responses) > Prepare tests for allowing addition of HTTP headers to management console responses > ----------------------------------------------------------------------------------- > > Key: WFLY-12839 > URL: https://issues.jboss.org/browse/WFLY-12839 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Tomas Terem > Assignee: Tomas Terem > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2422) Log protocols per class

by Diego Lovison (Jira)

Diego Lovison created JGRP-2422: ----------------------------------- Summary: Log protocols per class Key: JGRP-2422 URL: https://issues.jboss.org/browse/JGRP-2422 Project: JGroups Issue Type: Enhancement Affects Versions: 4.1.8 Reporter: Diego Lovison Assignee: Bela Ban As a developer I would like to configure the protocols logs per class name {noformat} org.jgroups.protocols.MERGE3=TRACE org.jgroups.protocols.FD_ALL=TRACE org.jgroups.protocols.VERIFY_SUSPECT=TRACE org.jgroups=DEBUG {noformat} All class will be using DEBUG except MERGE3, FD_ALL and VERIFY_SUSPECT that will be using TRACE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2422) Log protocols per class

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/JGRP-2422?page=com.atlassian.jira.plugin.... ] Diego Lovison reassigned JGRP-2422: ----------------------------------- Assignee: Diego Lovison (was: Bela Ban) > Log protocols per class > ----------------------- > > Key: JGRP-2422 > URL: https://issues.jboss.org/browse/JGRP-2422 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.1.8 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > As a developer I would like to configure the protocols logs per class name > {noformat} > org.jgroups.protocols.MERGE3=TRACE > org.jgroups.protocols.FD_ALL=TRACE > org.jgroups.protocols.VERIFY_SUSPECT=TRACE > org.jgroups=DEBUG > {noformat} > All class will be using DEBUG except MERGE3, FD_ALL and VERIFY_SUSPECT that will be using TRACE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-276) Boot time of application built via S2I is much longer than in before-Galleon times

by Martin Svehla (Jira)

[ https://issues.jboss.org/browse/WFWIP-276?page=com.atlassian.jira.plugin.... ] Martin Svehla commented on WFWIP-276: ------------------------------------- [~jdenise] you wrote in one of the previous comments that we need analysis of the solution. I think that having some kind of description of the fix and figuring out all its impacts is argument for making this into RFE. It's up to us how much we document for the end users, but it doesn't sound as just an "implementation detail". > Boot time of application built via S2I is much longer than in before-Galleon times > ---------------------------------------------------------------------------------- > > Key: WFWIP-276 > URL: https://issues.jboss.org/browse/WFWIP-276 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > Attachments: test-app.zip > > > As a consequence of Galleon RFEs EAP7-891 and mainly EAP7-1216 there is big difference in pod with EAP application start up time which requires S2I configuration. > This is an overview of quick comparison of average boot times of the application pods of the attached test app (we are not interested in build/deploy pod times etc): > ||17.0-6||pod time||EAP boot||config time > |#1 | 8283|6128|2155 > |#2 | 9446|7548|1898 > |#3 | 8767|6871| 1896 > |#4 | 8568|6272| 2296 > |#5 | 8000 |6362|1638 > ||average ||8613ms||6636ms||1977ms > ||18.0-7||pod time||EAP boot||config time > |#1 |13769|5716|8053 > |#2 |13362|5952|7410 > |#3 |14261|6093|8168 > |#4 |14322|6135|8187 > |#5 |13921|6326|7595 > ||average||13927ms||6044ms||7883ms > pod time = time from the pod start until EAP is fully booted (log contains {{started in ..}}) > EAP boot = time of boot EAP itself == {{started in ..}} > config time = the difference of previou timess = anything before EAP boot begins > Again we are talking here about the time needed for prepared application image to full start. We can clearly see the EAP boot times are comparable between 17 and 18 images but the configs times are almost 4 times longer with CD18 images. > This is very unfortunate as in my point of view the pod boot time is the most critical time for our users - they would typically prepare the app images only once in a time but their application can scale up and down many times during its uptime. > The cause of this that when S2I is needed with image 18.0+ the part of the configuration that was previously done during S2I build just once is now processed on *each* pod start. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4767) Fix error-popover position on simulation/background grids

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4767?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4767: ------------------------------------- Description: When there is only one column on the grid, the popover is show to the left. But if there is not enough space to the left, the popover is not visible. Proposed solution, for this situation, is to show the popover _above_ the cell. The final position preference order will be (respect the cell): RIGHT -> LEFT -> ABOVE was: When there is only one column on the grid, the popover is show to the left. But if there is not enough space to the left, the popover is not visible. Proposed solution, for this situation, is to show the popover _below_ the cell. If there is not space below, the the popover will be shown _above_. The final position preference order will be (respect the cell): RIGTH -> LEFT -> BELOW -> ABOVE > Fix error-popover position on simulation/background grids > --------------------------------------------------------- > > Key: DROOLS-4767 > URL: https://issues.jboss.org/browse/DROOLS-4767 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > When there is only one column on the grid, the popover is show to the left. But if there is not enough space to the left, the popover is not visible. > Proposed solution, for this situation, is to show the popover _above_ the cell. > The final position preference order will be (respect the cell): > RIGHT -> LEFT -> ABOVE > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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: ------------------------------- Steps to Reproduce: clone git@github.com:istraka/eap-microprofile-test-suite.git -b mp-health build WildFly run {code:java} mvn clean verify -Dtest=SubdeploymentHealthTest -Djboss.home=_path-to-wildfly_ -DfailIfNoTests=true {code} was: clone git@github.com:istraka/eap-microprofile-test-suite.git build WildFly run {code:java} mvn clean verify -Dtest=SubdeploymentHealthTest -Djboss.home=_path-to-wildfly_ -DfailIfNoTests=true {code} > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4834) Raise the timeout for concurrency tests

by Daniel Rosa (Jira)

[ https://issues.jboss.org/browse/DROOLS-4834?page=com.atlassian.jira.plugi... ] Daniel Rosa updated DROOLS-4834: -------------------------------- Git Pull Request: (was: https://github.com/kiegroup/drools/pull/2658) > Raise the timeout for concurrency tests > ---------------------------------------- > > Key: DROOLS-4834 > URL: https://issues.jboss.org/browse/DROOLS-4834 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1026) Service Details - Health - Missing fields

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1026: ------------------------------------- Summary: Service Details - Health - Missing fields Key: SWSQE-1026 URL: https://issues.jboss.org/browse/SWSQE-1026 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Automate all the missing fields in Health Overview of Service Details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4834) Raise the timeout for concurrency tests

by Daniel Rosa (Jira)

Daniel Rosa created DROOLS-4834: ----------------------------------- Summary: Raise the timeout for concurrency tests Key: DROOLS-4834 URL: https://issues.jboss.org/browse/DROOLS-4834 Project: Drools Issue Type: Bug Reporter: Daniel Rosa Assignee: Daniel Rosa On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 December 2019