April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2637) Invalid completion for ls and cd

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2637: -------------------------------------------- Summary: Invalid completion for ls and cd Key: WFCORE-2637 URL: https://issues.jboss.org/browse/WFCORE-2637 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise Some options that don't take any value are completed with a "=" character. For example: cd --hel<TAB> ==> cd --help= That has been caused by WFCORE-2123 that has removed the validation at completion time (that is a right thing). Prior to WFCORE-2123, the value completer of unamed argument was called and was failing due to invalid content (--hel is not a valid management address). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat SSL

by Arunraj SRM (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Arunraj SRM updated DROOLS-1516: -------------------------------- Component/s: build tools > GAV names are not coming properly when running the tomcat SSL > ------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Edson Tirelli > Priority: Blocker > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat SSL

by Arunraj SRM (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Arunraj SRM updated DROOLS-1516: -------------------------------- Issue Type: Bug (was: Feature Request) > GAV names are not coming properly when running the tomcat SSL > ------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Edson Tirelli > Priority: Blocker > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-81) Baseline #3

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-81?page=com.atlassian.jira.plu... ] viet nguyen edited comment on HAWKULARQE-81 at 4/6/17 1:07 PM: --------------------------------------------------------------- [^promgen-analytic-12hr.png] gives a snapshot of raw metrics tallies during a 12 hour run of 230 pods. Grafana dashboard url: http://hawkular-grafana-analytics.cloud2.jonqe.lab.eng.bos.redhat.com/das... (data may be pursed automatically after 14 days) Expected raw data points per 15 minute interval: 30 Observations: - As seen in the top graph raw metrics dip below 20 - there are metrics definitions but 0 data for some pods - I suspect the dips were caused by pod restarts but that is not the case. I randomly selected 2 pods, 1 with restart and 1 without restart and graph their data counts. Next step: - store metrics id by pod name as oppose to pod UID for easier cross references with output of oc commands - reduce the number of pod to see if there are still dips was (Author: vietn): [^promgen-analytic-12hr.png] gives a snapshot of raw metrics tallies during a 12 hour run of 230 pods. Expected raw data points per 15 minute interval: 30 Observations: - As seen in the top graph raw metrics dip below 20 - there are metrics definitions but 0 data for some pods - I suspect the dips were caused by pod restarts but that is not the case. I randomly selected 2 pods, 1 with restart and 1 without restart and graph their data counts. Next step: - store metrics id by pod name as oppose to pod UID for easier cross references with output of oc commands - reduce the number of pod to see if there are still dips > Baseline #3 > ----------- > > Key: HAWKULARQE-81 > URL: https://issues.jboss.org/browse/HAWKULARQE-81 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: viet nguyen > Assignee: viet nguyen > Attachments: March28_0200_raw.zip, promgen-analytic-12hr.png > > > * Run pyme on master to eliminate vpn slowness > * Fix query start-end window > * Update pyme endpoint to increase metrics to 30 (currently 2) > * insert metrics tallies into a separate Hawkular Metrics instance and use Grafana as a visual tool -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-81) Baseline #3

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-81?page=com.atlassian.jira.plu... ] viet nguyen commented on HAWKULARQE-81: --------------------------------------- [^promgen-analytic-12hr.png] gives a snapshot of raw metrics tallies during a 12 hour run of 230 pods. Expected raw data points per 15 minute interval: 30 Observations: - As seen in the top graph raw metrics dip below 20 - there are metrics definitions but 0 data for some pods - I suspect the dips were caused by pod restarts but that is not the case. I randomly selected 2 pods, 1 with restart and 1 without restart and graph their data counts. Next step: - store metrics id by pod name as oppose to pod UID for easier cross references with output of oc commands - reduce the number of pod to see if there are still dips > Baseline #3 > ----------- > > Key: HAWKULARQE-81 > URL: https://issues.jboss.org/browse/HAWKULARQE-81 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: viet nguyen > Assignee: viet nguyen > Attachments: March28_0200_raw.zip, promgen-analytic-12hr.png > > > * Run pyme on master to eliminate vpn slowness > * Fix query start-end window > * Update pyme endpoint to increase metrics to 30 (currently 2) > * insert metrics tallies into a separate Hawkular Metrics instance and use Grafana as a visual tool -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-81) Baseline #3

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-81?page=com.atlassian.jira.plu... ] viet nguyen updated HAWKULARQE-81: ---------------------------------- Attachment: promgen-analytic-12hr.png > Baseline #3 > ----------- > > Key: HAWKULARQE-81 > URL: https://issues.jboss.org/browse/HAWKULARQE-81 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: viet nguyen > Assignee: viet nguyen > Attachments: March28_0200_raw.zip, promgen-analytic-12hr.png > > > * Run pyme on master to eliminate vpn slowness > * Fix query start-end window > * Update pyme endpoint to increase metrics to 30 (currently 2) > * insert metrics tallies into a separate Hawkular Metrics instance and use Grafana as a visual tool -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2636) Upgrade WildFly Elytron Tool to 1.0.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2636: ---------------------------------------- Summary: Upgrade WildFly Elytron Tool to 1.0.0.Beta1 Key: WFCORE-2636 URL: https://issues.jboss.org/browse/WFCORE-2636 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta14 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2635) Upgrade WildFly Elytron to 1.1.0.Beta35

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2635: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.Beta35 Key: WFCORE-2635 URL: https://issues.jboss.org/browse/WFCORE-2635 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta14 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2514) standalone.sh can hang on gc log back up moves

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2514?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2514: ------------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1426647|https://bugzilla.redhat.com/show_bug.cgi?id=1426647] from MODIFIED to ON_QA > standalone.sh can hang on gc log back up moves > ---------------------------------------------- > > Key: WFCORE-2514 > URL: https://issues.jboss.org/browse/WFCORE-2514 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Beta7 > Reporter: Aaron Ogburn > Assignee: Aaron Ogburn > Fix For: 3.0.0.Beta8 > > > If it doesn't have proper write access to an existing backupgc.log, standalone.sh will hang. The file mv should use the -f flag. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2634) Deprecate AttributeDefinitions constructors that don't use a builder

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2634: ---------------------------------------- Summary: Deprecate AttributeDefinitions constructors that don't use a builder Key: WFCORE-2634 URL: https://issues.jboss.org/browse/WFCORE-2634 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry The number of users of AD constructor variants other than the ones that use a builder a quite low. So deprecate the remaining non-deprecated constructors to make it easier to remove them as we lock down our supported API. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017