March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-37) [QE] - SWS-51 - View Istio's services details

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-37?page=com.atlassian.jira.plugin.s... ] Sunil kondkar resolved SWSQE-37. -------------------------------- Resolution: Done > [QE] - SWS-51 - View Istio's services details > --------------------------------------------- > > Key: SWSQE-37 > URL: https://issues.jboss.org/browse/SWSQE-37 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > > Test subtasks of https://issues.jboss.org/browse/SWS-51 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Radoslav Husar edited comment on WFLY-6634 at 3/14/18 9:13 AM: --------------------------------------------------------------- [~rjanik] It's actually 3 WFLY issues (there is also WFLY-9860). With current process, only whole features can be merged thus you are more likely to see more Jiras for a single RFE. There is no reason why there would be 1:1 coupling RFE with upstream Jira. There is very little to test within scope of WFLY-6634 as its not supported as a feature. That being said, we can do whatever works best for QE, but I am just saying we cannot create RFE for things that are not supported features. was (Author: rhusar): [~rjanik] It's actually 3 WFLY issues (there is also WFLY-9860). With current process, only whole features can be merged thus you are more likely to see more Jiras for a single RFE. There is no reason why there would be 1:1 coupling RFE with upstream Jira. There is very little to test within scope of WFLY-6634 as its not supported as a feature. That being said, we can do whatever works best for QE, but I am just saying we cannot create RFE for things that are not features. > Add remote-cache-container configuration to Infinispan subsystem > ---------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFLY-10014 at 3/14/18 9:13 AM: ---------------------------------------------------------------- Artemis 1.5.5.009 is missing: {code} /** * Some configuration values can contain commas (e.g. enabledProtocols, enabledCipherSuites, etc.). * To support config values with commas, the commas in the values must be escaped (e.g. "\\,") so that * the commas used to separate configs for different connectors can still function as designed. */ String commaPlaceHolder = UUID.randomUUID().toString(); String replaced = config.replace("\\,", commaPlaceHolder); ... {code} in ActiveMQRaUtils.parseConfig(). Looks like there was a fix for this to Artemis 2.x but was not backported to Artemis 1.x. Compare: https://github.com/rh-messaging/jboss-activemq-artemis/blob/1.5.5.jbossor... and https://github.com/apache/activemq-artemis/blob/master/artemis-ra/src/mai... was (Author: mnovak): Artemis 1.5.5.009 is missing: {code} /** * Some configuration values can contain commas (e.g. enabledProtocols, enabledCipherSuites, etc.). * To support config values with commas, the commas in the values must be escaped (e.g. "\\,") so that * the commas used to separate configs for different connectors can still function as designed. */ String commaPlaceHolder = UUID.randomUUID().toString(); String replaced = config.replace("\\,", commaPlaceHolder); ... {code} in ActiveMQRaUtils.parseConfig(). Looks like there was a fix for this to Artemis 2.x but was not backported to Artemis 1.x. > Unable to configure comma delimited enabled-protocols in remote-connector > ------------------------------------------------------------------------- > > Key: WFLY-10014 > URL: https://issues.jboss.org/browse/WFLY-10014 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Nagaraju Chitimilla > Assignee: Jeff Mesnil > Priority: Critical > > When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector > {noformat} > <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/> > {noformat} > But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails: > {code:java} > Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12 > at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205) > at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342) > ... 18 more > {code} > I set this as critical as it prevent setting more then one allowed SSLContext protocol. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Radoslav Husar edited comment on WFLY-6634 at 3/14/18 9:12 AM: --------------------------------------------------------------- [~rjanik] It's actually 3 WFLY issues (there is also WFLY-9860). With current process, only whole features can be merged thus you are more likely to see more Jiras for a single RFE. There is no reason why there would be 1:1 coupling RFE with upstream Jira. There is very little to test within scope of WFLY-6634 as its not supported as a feature. That being said, we can do whatever works best for QE, but I am just saying we cannot create RFE for things that are not features. was (Author: rhusar): [~rjanik] It's actually 3 WFLY issues (there is also WFLY-9860). With current process, only whole features can be merged thus you are more likely to see more Jiras for a single RFE. There is no reason why there would be 1:1 coupling RFE with upstream Jira. There is very little to test within scope of WFLY-6634 as its not supported as a feature. > Add remote-cache-container configuration to Infinispan subsystem > ---------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10014: --------------------------------------- Artemis 1.5.5.009 is missing: {code} /** * Some configuration values can contain commas (e.g. enabledProtocols, enabledCipherSuites, etc.). * To support config values with commas, the commas in the values must be escaped (e.g. "\\,") so that * the commas used to separate configs for different connectors can still function as designed. */ String commaPlaceHolder = UUID.randomUUID().toString(); String replaced = config.replace("\\,", commaPlaceHolder); ... {code} in ActiveMQRaUtils.parseConfig(). Looks like there was a fix for this to Artemis 2.x but was not backported to Artemis 1.x. > Unable to configure comma delimited enabled-protocols in remote-connector > ------------------------------------------------------------------------- > > Key: WFLY-10014 > URL: https://issues.jboss.org/browse/WFLY-10014 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Nagaraju Chitimilla > Assignee: Jeff Mesnil > Priority: Critical > > When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector > {noformat} > <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/> > {noformat} > But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails: > {code:java} > Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12 > at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205) > at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342) > ... 18 more > {code} > I set this as critical as it prevent setting more then one allowed SSLContext protocol. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6634: -------------------------------------- [~rjanik] It's actually 3 WFLY issues (there is also WFLY-9860). With current process, only whole features can be merged thus you are more likely to see more Jiras for a single RFE. There is no reason why there would be 1:1 coupling RFE with upstream Jira. There is very little to test within scope of WFLY-6634 as its not supported as a feature. > Add remote-cache-container configuration to Infinispan subsystem > ---------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-36) Automation To Compare Actual vs Expected Services JSON

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-36?page=com.atlassian.jira.plugin.s... ] Matt Mahoney closed SWSQE-36. ----------------------------- Resolution: Done > Automation To Compare Actual vs Expected Services JSON > ------------------------------------------------------ > > Key: SWSQE-36 > URL: https://issues.jboss.org/browse/SWSQE-36 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Create simple/prototype script to compare Actual SWS JSON vs Expected ISTIO Services Graph JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Richard Janík edited comment on WFLY-6634 at 3/14/18 8:59 AM: -------------------------------------------------------------- [~rhusar], that was WFLY-9294 we were talking about. Now I see you track both these WFLY issues under EAP7-942. This is too big for one RFE - there should be one feature per one RFE, so we'd have a new EAP7 issue, which EAP7-942 would depend upon. EAP7-942 goes to [~mvinkler], the new RFE goes to me. WDYT? The new RFE will be about the {{remote-cache-container}} configuration, EAP7-942 is about the JDG related scenarios. was (Author: rjanik): [~rhusar], that was WFLY-9294 we were talking about. Now I see you track both these WFLY issues under EAP7-942. This is too big for one RFE - there should be one feature per one RFE, so we'd have a new EAP7 issue, which EAP7-942 would depend upon. EAP7-942 goes to [~mvinkler], the new RFE goes to me. WDYT? The new RFE will be about the [[remote-cache-container]] configuration, EAP7-942 is about the JDG related scenarios. > Add remote-cache-container configuration to Infinispan subsystem > ---------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem

by Richard Janík (JIRA)

[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-6634: ------------------------------------- [~rhusar], that was WFLY-9294 we were talking about. Now I see you track both these WFLY issues under EAP7-942. This is too big for one RFE - there should be one feature per one RFE, so we'd have a new EAP7 issue, which EAP7-942 would depend upon. EAP7-942 goes to [~mvinkler], the new RFE goes to me. WDYT? The new RFE will be about the [[remote-cache-container]] configuration, EAP7-942 is about the JDG related scenarios. > Add remote-cache-container configuration to Infinispan subsystem > ---------------------------------------------------------------- > > Key: WFLY-6634 > URL: https://issues.jboss.org/browse/WFLY-6634 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Need to establish schema/model. > We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2388) DMN Namespace unmarshalling differs from standard one when calling DMNValidator.validate method with File param

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2388?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2388: ------------------------------------- Assignee: Fedor Gavrilov (was: Edson Tirelli) > DMN Namespace unmarshalling differs from standard one when calling DMNValidator.validate method with File param > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2388 > URL: https://issues.jboss.org/browse/DROOLS-2388 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Tibor Zimányi > Assignee: Fedor Gavrilov > Priority: Minor > > When using DMNValidator.validate method that takes a DMN file as a parameter, the validation results are sometimes different from results of validate method that takes Definitions as an input parameter. The main difference looks to be namespace parsing. > Reproducer can be found here: https://github.com/kiegroup/drools/pull/1814 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 March 2018