March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2420: -------------------------------------- Summary: [DMN Designer] Hit Policy Collect does not need an Aggregation function Key: DROOLS-2420 URL: https://issues.jboss.org/browse/DROOLS-2420 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10110) Connector PoolConfigurationRWHandler does not handle undefined values for attributes without default values

by Flavia Rainone (JIRA)

Flavia Rainone created WFLY-10110: ------------------------------------- Summary: Connector PoolConfigurationRWHandler does not handle undefined values for attributes without default values Key: WFLY-10110 URL: https://issues.jboss.org/browse/WFLY-10110 Project: WildFly Issue Type: Bug Reporter: Flavia Rainone Assignee: Flavia Rainone Currently, the attribute BLOCKING_TIMEOUT_WAIT_MILLIS and INITIAL_POOL_SIZE do not have a default value and require a special treatment for handling undefined values being set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-80) Automated deployment of Istio Traffice Management

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-80?page=com.atlassian.jira.plugin.s... ] Matt Mahoney reassigned SWSQE-80: --------------------------------- Assignee: Matt Mahoney (was: Michael Foley) > Automated deployment of Istio Traffice Management > ------------------------------------------------- > > Key: SWSQE-80 > URL: https://issues.jboss.org/browse/SWSQE-80 > Project: Swift Sunshine QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration. > Istio documentation reference: [link title|https://istio.io/docs/tasks/traffic-management/] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1552) Coverity, Reliance on default encoding in DigestAuthenticationMechanism.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1552?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1552: ------------------------------- Component/s: Authentication Mechanisms > Coverity, Reliance on default encoding in DigestAuthenticationMechanism. > ------------------------------------------------------------------------ > > Key: ELY-1552 > URL: https://issues.jboss.org/browse/ELY-1552 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.4.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Minor > > In org.wildfly.security.http.impl.DigestAuthenticationMechanism.digestUriMatchesRequestUri(org.wildfly.security.http.HttpServerRequest, byte[]): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. > {code} > private boolean digestUriMatchesRequestUri(HttpServerRequest request, byte[] digestUri) { > if (!validateUri) { > return true; > } > java.net.URI requestURI = request.getRequestURI(); > String digestUriStr = new String(digestUri); > {code} > https://scan7.coverity.com/reports.htm#v20225/p11778/fileInstanceId=49333... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10109) [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10109?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-10109: ---------------------------------- Steps to Reproduce: {code} export DISABLE_TRACE_LOGS=false git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout 68b9d2581640574d4d04926cf2d576fe756bca0d groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/273//artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn -D-Deap7.clients.version=7.1521816809-SNAPSHOT -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1521816809-SNAPSHOT clean install -Dtest=RemoteJcaTestCase#testRemoteJcaWihtDefaultJGroupsCluster {code} was: {code} export DISABLE_TRACE_LOGS=false git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/273//artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn -D-Deap7.clients.version=7.1521816809-SNAPSHOT -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1521816809-SNAPSHOT clean install -Dtest=RemoteJcaTestCase#testRemoteJcaWihtDefaultJGroupsCluster {code} > [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10109 > URL: https://issues.jboss.org/browse/WFLY-10109 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > Sometimes happens that MDB does not start to consume messages from remote server. There are not warning or error messages in log. > Test Scenario: > * Start server with deployed InQueue and OutQueue > * Start 2nd server with configured pooled-connection-factory to connect to 1st server > * Deploy MDB to 2nd server - mdb is consuming messages from InQueue and sending to OutQueue > * Start sending messages to InQueue to 1st server > * Let MDB processing messages from InQueue > * Start consuming messages from OutQueue from 1st server > Pass Criteria: There is the same number of sent and received messages > Actual Result: Sometimes happens that Mdb does not start to consume messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10109) [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10109?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-10109: ---------------------------------- Steps to Reproduce: {code} export DISABLE_TRACE_LOGS=false git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/273//artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn -D-Deap7.clients.version=7.1521816809-SNAPSHOT -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1521816809-SNAPSHOT clean install -Dtest=RemoteJcaTestCase#testRemoteJcaWihtDefaultJGroupsCluster {code} > [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10109 > URL: https://issues.jboss.org/browse/WFLY-10109 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > Sometimes happens that MDB does not start to consume messages from remote server. There are not warning or error messages in log. > Test Scenario: > * Start server with deployed InQueue and OutQueue > * Start 2nd server with configured pooled-connection-factory to connect to 1st server > * Deploy MDB to 2nd server - mdb is consuming messages from InQueue and sending to OutQueue > * Start sending messages to InQueue to 1st server > * Let MDB processing messages from InQueue > * Start consuming messages from OutQueue from 1st server > Pass Criteria: There is the same number of sent and received messages > Actual Result: Sometimes happens that Mdb does not start to consume messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1552) Coverity, Reliance on default encoding in DigestAuthenticationMechanism.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-1552: ---------------------------------- Summary: Coverity, Reliance on default encoding in DigestAuthenticationMechanism. Key: ELY-1552 URL: https://issues.jboss.org/browse/ELY-1552 Project: WildFly Elytron Issue Type: Bug Affects Versions: 1.2.4.Final Reporter: Ilia Vassilev Assignee: Ilia Vassilev Priority: Minor In org.wildfly.security.http.impl.DigestAuthenticationMechanism.digestUriMatchesRequestUri(org.wildfly.security.http.HttpServerRequest, byte[]): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. {code} private boolean digestUriMatchesRequestUri(HttpServerRequest request, byte[] digestUri) { if (!validateUri) { return true; } java.net.URI requestURI = request.getRequestURI(); String digestUriStr = new String(digestUri); {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1552) Coverity, Reliance on default encoding in DigestAuthenticationMechanism.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1552?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1552: ------------------------------- Description: In org.wildfly.security.http.impl.DigestAuthenticationMechanism.digestUriMatchesRequestUri(org.wildfly.security.http.HttpServerRequest, byte[]): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. {code} private boolean digestUriMatchesRequestUri(HttpServerRequest request, byte[] digestUri) { if (!validateUri) { return true; } java.net.URI requestURI = request.getRequestURI(); String digestUriStr = new String(digestUri); {code} https://scan7.coverity.com/reports.htm#v20225/p11778/fileInstanceId=49333... was: In org.wildfly.security.http.impl.DigestAuthenticationMechanism.digestUriMatchesRequestUri(org.wildfly.security.http.HttpServerRequest, byte[]): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. {code} private boolean digestUriMatchesRequestUri(HttpServerRequest request, byte[] digestUri) { if (!validateUri) { return true; } java.net.URI requestURI = request.getRequestURI(); String digestUriStr = new String(digestUri); {code} > Coverity, Reliance on default encoding in DigestAuthenticationMechanism. > ------------------------------------------------------------------------ > > Key: ELY-1552 > URL: https://issues.jboss.org/browse/ELY-1552 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.4.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Minor > > In org.wildfly.security.http.impl.DigestAuthenticationMechanism.digestUriMatchesRequestUri(org.wildfly.security.http.HttpServerRequest, byte[]): Found a call to a method which will perform a byte to String (or String to byte) conversion, and will assume that the default platform encoding is suitable. > {code} > private boolean digestUriMatchesRequestUri(HttpServerRequest request, byte[] digestUri) { > if (!validateUri) { > return true; > } > java.net.URI requestURI = request.getRequestURI(); > String digestUriStr = new String(digestUri); > {code} > https://scan7.coverity.com/reports.htm#v20225/p11778/fileInstanceId=49333... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10109) [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-10109: ------------------------------------- Summary: [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups Key: WFLY-10109 URL: https://issues.jboss.org/browse/WFLY-10109 Project: WildFly Issue Type: Bug Components: JMS Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Blocker Sometimes happens that MDB does not start to consume messages from remote server. There are not warning or error messages in log. Test Scenario: * Start server with deployed InQueue and OutQueue * Start 2nd server with configured pooled-connection-factory to connect to 1st server * Deploy MDB to 2nd server - mdb is consuming messages from InQueue and sending to OutQueue * Start sending messages to InQueue to 1st server * Let MDB processing messages from InQueue * Start consuming messages from OutQueue from 1st server Pass Criteria: There is the same number of sent and received messages Actual Result: Sometimes happens that Mdb does not start to consume messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-80) Automated deployment of Istio Traffice Management

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-80?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-80: ------------------------------ Team: Infrastructure Sprint: Kiali QE Sprint 3 > Automated deployment of Istio Traffice Management > ------------------------------------------------- > > Key: SWSQE-80 > URL: https://issues.jboss.org/browse/SWSQE-80 > Project: Swift Sunshine QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > > As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration. > Istio documentation reference: [link title|https://istio.io/docs/tasks/traffic-management/] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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