March 2018 - jboss-jira - Jboss List Archives

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-64?page=com.atlassian.jira.plugin.s... ] Matt Mahoney resolved SWSQE-64. ------------------------------- Resolution: Done > [QE] SWS-226 > ------------ > > Key: SWSQE-64 > URL: https://issues.jboss.org/browse/SWSQE-64 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Report SWS version and status information to users > [link title|https://issues.jboss.org/browse/SWS-226] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2237) Turn on CheckStyle for dmn editor

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2237?page=com.atlassian.jira.plugi... ] Jozef Marko reopened DROOLS-2237: --------------------------------- > Turn on CheckStyle for dmn editor > --------------------------------- > > Key: DROOLS-2237 > URL: https://issues.jboss.org/browse/DROOLS-2237 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.6.0.Final > > > Turn of the CheckStyle control of imports and licences for the dmn editor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2237) Turn on CheckStyle for dmn editor

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2237?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2237: -------------------------------- Sprint: 2018 Week 11-12 > Turn on CheckStyle for dmn editor > --------------------------------- > > Key: DROOLS-2237 > URL: https://issues.jboss.org/browse/DROOLS-2237 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.6.0.Final > > > Turn of the CheckStyle control of imports and licences for the dmn editor. -- 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: ------------------------------ Description: 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/] was: 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. > 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

[JBoss JIRA] (SWSQE-60) [QE] - SWS-276 - Provide service Health as a separate endpoint

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-60?page=com.atlassian.jira.plugin.s... ] Sunil kondkar resolved SWSQE-60. -------------------------------- Resolution: Done > [QE] - SWS-276 - Provide service Health as a separate endpoint > -------------------------------------------------------------- > > Key: SWSQE-60 > URL: https://issues.jboss.org/browse/SWSQE-60 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > > User Story https://issues.jboss.org/browse/SWS-276 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2417) Some concurrency tests are missing timeouts

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2417: ------------------------------------- Summary: Some concurrency tests are missing timeouts Key: DROOLS-2417 URL: https://issues.jboss.org/browse/DROOLS-2417 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.6.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Some of the tests from package org.drools.compiler.integrationtests.concurrency [1] miss timetout in the @Test annotation. This can cause build hangs when something wrong happens during a test. [1] https://github.com/baldimir/drools/tree/6b24ae59ae21bc0146d11bcb7606d1b42... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2253: --------------------------- Fix Version/s: 4.0.12 > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.12 > > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-10094: ------------------------------------- Summary: [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 Key: WFLY-10094 URL: https://issues.jboss.org/browse/WFLY-10094 Project: WildFly Issue Type: Bug Components: JMS Reporter: Miroslav Novak Assignee: Jeff Mesnil Priority: Blocker LibAIO does not get loaded on RHEL 6 x86_64: {code} [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /tmp/jboss-eap JAVA: java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= ... 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal ... {code} libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10093) mod_cluster "max-attempts" attribute description is incorrect

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10093?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10093: ---------------------------------- Description: This is very easy to overlook because the attribute is extremely poorly named and missing from MCMP definition [1] completely. This is because mod_cluster aligned nomenclature with httpd mod_proxy's [2] which defines maxattempts as: *Maximum number of failover attempts before giving up.* and not total number attempts. This means, that value od 0 is a valid value meaning no retry. [1] https://developer.jboss.org/docs/DOC-11425 [2] https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass was: This is very easy to overlook because the attribute is extremely poorly named and missing from MCMP definition [1] completely. This is because mod_cluster aligned nomenclature with httpd mod_proxy's [2] which defines maxattempts as: *Maximum number of failover attempts before giving up.* [1] https://developer.jboss.org/docs/DOC-11425 [2] https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass > mod_cluster "max-attempts" attribute description is incorrect > ------------------------------------------------------------- > > Key: WFLY-10093 > URL: https://issues.jboss.org/browse/WFLY-10093 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 12.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > This is very easy to overlook because the attribute is extremely poorly named and missing from MCMP definition [1] completely. This is because mod_cluster aligned nomenclature with httpd mod_proxy's [2] which defines maxattempts as: > *Maximum number of failover attempts before giving up.* > and not total number attempts. This means, that value od 0 is a valid value meaning no retry. > [1] https://developer.jboss.org/docs/DOC-11425 > [2] https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10093) mod_cluster "max-attempts" attribute description is incorrect

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10093?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10093: ---------------------------------- Description: This is very easy to overlook because the attribute is extremely poorly named and missing from MCMP definition [1] completely. This is because mod_cluster aligned nomenclature with httpd mod_proxy's [2] which defines maxattempts as: *Maximum number of failover attempts before giving up.* [1] https://developer.jboss.org/docs/DOC-11425 [2] https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass > mod_cluster "max-attempts" attribute description is incorrect > ------------------------------------------------------------- > > Key: WFLY-10093 > URL: https://issues.jboss.org/browse/WFLY-10093 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 12.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > This is very easy to overlook because the attribute is extremely poorly named and missing from MCMP definition [1] completely. This is because mod_cluster aligned nomenclature with httpd mod_proxy's [2] which defines maxattempts as: > *Maximum number of failover attempts before giving up.* > [1] https://developer.jboss.org/docs/DOC-11425 > [2] https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass -- 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