December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4246) FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/WFCORE-4246?page=com.atlassian.jira.plugi... ] Masafumi Miura updated WFCORE-4246: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3615 > FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4246 > URL: https://issues.jboss.org/browse/WFCORE-4246 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 7.0.0.Final > Reporter: Masafumi Miura > Assignee: ehsavoie Hugonnet > Priority: Minor > > Even if scanEnabled="false" is specified in the deployment-scanner subsystem, a deployment marker can be created for files located under the deployment-scanner directory. This happens when deploying an application which has the same filename to the file through the management CLI. > This behavior did not happen in EAP 6.4.x, but this happens since EAP 7.x because of FileSystemDeploymentService#handleNotification() processing. > I think this behavior itself does not have a negative effect, so this is a minor issue. However, it's better to avoid creating an unneeded marker file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4246) FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/WFCORE-4246?page=com.atlassian.jira.plugi... ] Masafumi Miura moved JBEAP-16000 to WFCORE-4246: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4246 (was: JBEAP-16000) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Deployment Scanner (was: Deployment Scanner) Affects Version/s: 7.0.0.Final (was: 7.1.5.GA) > FileSystemDeploymentService#handleNotification() can create an unneeded deployment marker file even if scanEnabled="false" is specified > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4246 > URL: https://issues.jboss.org/browse/WFCORE-4246 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 7.0.0.Final > Reporter: Masafumi Miura > Assignee: ehsavoie Hugonnet > Priority: Minor > > Even if scanEnabled="false" is specified in the deployment-scanner subsystem, a deployment marker can be created for files located under the deployment-scanner directory. This happens when deploying an application which has the same filename to the file through the management CLI. > This behavior did not happen in EAP 6.4.x, but this happens since EAP 7.x because of FileSystemDeploymentService#handleNotification() processing. > I think this behavior itself does not have a negative effect, so this is a minor issue. However, it's better to avoid creating an unneeded marker file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-540) Problem on Kiali Traffic Checker

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-540?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-540: ------------------------------------ Fixed, in master. Will leave open for time being to be sure there are no issues. > Problem on Kiali Traffic Checker > -------------------------------- > > Key: SWSQE-540 > URL: https://issues.jboss.org/browse/SWSQE-540 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Matt Mahoney > Priority: Major > > A problem on Kiali Checker is preventing the jobs to finish successfully. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 154 0 --:--:-- --:--:-- --:--:-- 154 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 155 0 --:--:-- --:--:-- --:--:-- 155 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > scripts/kiali/testscript.sh: line 315: [: =: unary operator expected > Timed out after 10 minutes.. waiting for Traffic on Bookinfo Graph. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-540) Problem on Kiali Traffic Checker

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-540?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-540: ------------------------------------ http://git.app.eng.bos.redhat.com/git/kiali-qe-utils.git/diff/?h=SWSQE-540 > Problem on Kiali Traffic Checker > -------------------------------- > > Key: SWSQE-540 > URL: https://issues.jboss.org/browse/SWSQE-540 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Matt Mahoney > Priority: Major > > A problem on Kiali Checker is preventing the jobs to finish successfully. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 154 0 --:--:-- --:--:-- --:--:-- 154 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 155 0 --:--:-- --:--:-- --:--:-- 155 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > scripts/kiali/testscript.sh: line 315: [: =: unary operator expected > Timed out after 10 minutes.. waiting for Traffic on Bookinfo Graph. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-532) Workload Details - Destination Service Tab.

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-532?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-532. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/113 > Workload Details - Destination Service Tab. > ------------------------------------------- > > Key: SWSQE-532 > URL: https://issues.jboss.org/browse/SWSQE-532 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Automate https://issues.jboss.org/browse/KIALI-1140 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-540) Problem on Kiali Traffic Checker

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-540: --------------------------------------------- Summary: Problem on Kiali Traffic Checker Key: SWSQE-540 URL: https://issues.jboss.org/browse/SWSQE-540 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley A problem on Kiali Checker is preventing the jobs to finish successfully. http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... Waiting for Bookinfo Graph Node-Edges (Edge count: 0). Check that Traffic Generator is creating Bookinfo Graph Node-Edges... Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 35 100 35 0 0 154 0 --:--:-- --:--:-- --:--:-- 154 Waiting for Bookinfo Graph Node-Edges (Edge count: 0). Check that Traffic Generator is creating Bookinfo Graph Node-Edges... Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 35 100 35 0 0 155 0 --:--:-- --:--:-- --:--:-- 155 Waiting for Bookinfo Graph Node-Edges (Edge count: 0). scripts/kiali/testscript.sh: line 315: [: =: unary operator expected Timed out after 10 minutes.. waiting for Traffic on Bookinfo Graph. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-540) Problem on Kiali Traffic Checker

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-540?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-540: --------------------------------------------- Assignee: Matt Mahoney (was: Michael Foley) > Problem on Kiali Traffic Checker > -------------------------------- > > Key: SWSQE-540 > URL: https://issues.jboss.org/browse/SWSQE-540 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Matt Mahoney > Priority: Major > > A problem on Kiali Checker is preventing the jobs to finish successfully. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 154 0 --:--:-- --:--:-- --:--:-- 154 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 155 0 --:--:-- --:--:-- --:--:-- 155 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > scripts/kiali/testscript.sh: line 315: [: =: unary operator expected > Timed out after 10 minutes.. waiting for Traffic on Bookinfo Graph. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-540) Problem on Kiali Traffic Checker

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-540?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-540: ------------------------------------------ Team: Infrastructure (was: Infrastructure) Sprint: Kiali Sprint #15 > Problem on Kiali Traffic Checker > -------------------------------- > > Key: SWSQE-540 > URL: https://issues.jboss.org/browse/SWSQE-540 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Matt Mahoney > Priority: Major > > A problem on Kiali Checker is preventing the jobs to finish successfully. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Chec... > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 154 0 --:--:-- --:--:-- --:--:-- 154 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > Check that Traffic Generator is creating Bookinfo Graph Node-Edges... > Kiali Graph API Str: curl -k https://admin:admin@kiali-istio-system.openshift2.jonqe.lab.eng.bos.redha... > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > 100 35 100 35 0 0 155 0 --:--:-- --:--:-- --:--:-- 155 > Waiting for Bookinfo Graph Node-Edges (Edge count: 0). > scripts/kiali/testscript.sh: line 315: [: =: unary operator expected > Timed out after 10 minutes.. waiting for Traffic on Bookinfo Graph. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3407) Need to use one rule in each one of the agendas efficiently in Kie Drools 7.12

by Rafael Jordá (Jira)

Rafael Jordá created DROOLS-3407: ------------------------------------ Summary: Need to use one rule in each one of the agendas efficiently in Kie Drools 7.12 Key: DROOLS-3407 URL: https://issues.jboss.org/browse/DROOLS-3407 Project: Drools Issue Type: Enhancement Components: eclipse plugin Affects Versions: 7.12.0.Final Reporter: Rafael Jordá Assignee: Kris Verlaenen Fix For: 7.12.0.Final Hi, I'm working in a project using Drools in Eclipse. I need to solve the following issue and I was wondering if you could help me. I have a rule that needs to be triggered in each one of the agendas that I've defined in my drl file (it is a very important rule). First, I tried not to set an agenda for that rule, but it only got executed at the end of the last agenda. So the only thing that came to my mind was defining that rule in each one of the agendas, i.e., the same rule is repeated in all of them, which is not the most efficient solution. Is this a normal issue? Is there a better solution? Thanks. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-153) Remove finalization from Logger

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-153?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-153: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/112, https://github.com/jboss-logging/jboss-logmanager/pull/215 (was: https://github.com/jboss-logging/jboss-logmanager/pull/112) > Remove finalization from Logger > ------------------------------- > > Key: LOGMGR-153 > URL: https://issues.jboss.org/browse/LOGMGR-153 > Project: JBoss Log Manager > Issue Type: Sub-task > Components: core > Reporter: Philippe Marschall > Priority: Major > Fix For: 3.0.0.Final > > > Finalization has been [deprecated in Java 9|https://stuartmarks.wordpress.com/2017/04/17/deprecation-of-object-fina...] because of performance issues with the recommendation that people switch to PhantomReference. Unfortunately as part of LOGMGR-107 Logger now uses finalization. Fortunately thanks to the excellent ref package in wildly-common this can be fixed easily. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2018