August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-151) Avoid Trigger collisions - Sprint-65

by Michael Foley (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-151?page=com.atlassian.jira.pl... ] Michael Foley commented on HAWKULARQE-151: ------------------------------------------ Documenting test summary Enhancement (https://github.com/ManageIQ/manageiq-providers-hawkular/pull/22/files) Hawkular Board (https://issues.jboss.org/browse/HAWKULARQE-151) Test Plan ( 3 Test Cases (2 passed, 1 fail) Issues Found ManageIQ Latest Docker is not working RHEL 7.4 Atomic https://github.com/ManageIQ/manageiq/issues/15703 Hawkular Agent Unable to connect to Hawkular Services on Openshift https://github.com/hawkular/hawkular-services/issues/172 Events don’t show on Middleware Provider Timeline https://github.com/ManageIQ/manageiq/issues/15756 Tag Queries may produce Cassandra Busy Pool https://issues.jboss.org/projects/HWKALERTS/issues/HWKALERTS-275 > Avoid Trigger collisions - Sprint-65 > ------------------------------------ > > Key: HAWKULARQE-151 > URL: https://issues.jboss.org/browse/HAWKULARQE-151 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > > Avoid Trigger collisions when Hawkular is linked to multiple MIQ installations > Ref Sprint Review: https://www.youtube.com/watch?v=nXLLLv_QyP0&feature=em-subs_digest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9192) InfinispanLogger executorIgnored() has no effect

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9192?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9192: --------------------------------- Priority: Minor (was: Major) > InfinispanLogger executorIgnored() has no effect > ------------------------------------------------ > > Key: WFLY-9192 > URL: https://issues.jboss.org/browse/WFLY-9192 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Radoslav Husar > Priority: Minor > > The method isn't an @LogMessage method and its return value is unused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9192) InfinispanLogger executorIgnored() has no effect

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9192?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9192: --------------------------------- Affects Version/s: 11.0.0.Beta1 > InfinispanLogger executorIgnored() has no effect > ------------------------------------------------ > > Key: WFLY-9192 > URL: https://issues.jboss.org/browse/WFLY-9192 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Radoslav Husar > Priority: Minor > > The method isn't an @LogMessage method and its return value is unused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2565) Incorrect permission class-name should throw exception at runtime

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2565?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-2565: ------------------------------------- Assignee: Ilia Vassilev (was: ehsavoie Hugonnet) > Incorrect permission class-name should throw exception at runtime > ----------------------------------------------------------------- > > Key: WFCORE-2565 > URL: https://issues.jboss.org/browse/WFCORE-2565 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > > In case when some permission mapper (tried with constant-permission-mapper and simple-permission-mapper) includes permission with non-existent class-name then it seems that no exception is thrown during runtime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3167) option to filter out aged out patches from the patching history

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-3167: ----------------------------------------- Summary: option to filter out aged out patches from the patching history Key: WFCORE-3167 URL: https://issues.jboss.org/browse/WFCORE-3167 Project: WildFly Core Issue Type: Feature Request Components: CLI, Patching Affects Versions: 3.0.0.Beta30 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 3.0.0.CR1 show-history management operation (and patch history cli command) returns all the patches that have been applied to the installation even if some of them have been aged out by executing ageout-history management operation. In some cases it would be useful to filter out the aged out patches from the result, leaving only the patches that can actually be rolled back by a user. That could be achieved by adding an optional boolean parameter exclude-agedout (with default value false to preserve the current behavior) to show-history operation. The high level CLI command patch history could include an equivalent --exclude-agedout argument. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2207) Use of AUTH does not result in a SecurityException if another client does not use AUTH

by Mirko Streckenbach (JIRA)

[ https://issues.jboss.org/browse/JGRP-2207?page=com.atlassian.jira.plugin.... ] Mirko Streckenbach updated JGRP-2207: ------------------------------------- Summary: Use of AUTH does not result in a SecurityException if another client does not use AUTH (was: Use of AUTH does result in a SecurityException if another client does not use AUTH) > Use of AUTH does not result in a SecurityException if another client does not use AUTH > -------------------------------------------------------------------------------------- > > Key: JGRP-2207 > URL: https://issues.jboss.org/browse/JGRP-2207 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.4 > Reporter: Mirko Streckenbach > Assignee: Bela Ban > Fix For: 4.0.5 > > Attachments: JGroupsAuthExample.java, JGroupsAuthExample.java > > > If there are two members in a cluster, one with AUTH configured and started first, so it can become the coordinator and a second without AUTH, the documentation implies that the second should receive a SecurityException. Instead, it creates it's own cluster. This works as expected if the second member uses AUTH, but has a different SecurityToken. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9211) Route is only appended to session id when using ha profile

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9211?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9211: ------------------------------- Security: (was: Red Hat Internal) > Route is only appended to session id when using ha profile > ---------------------------------------------------------- > > Key: WFLY-9211 > URL: https://issues.jboss.org/browse/WFLY-9211 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 11.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > instance-id only works for profiles with ha: > {code:java} > <subsystem xmlns="urn:jboss:domain:undertow:4.0" instance-id="node1"> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9211) Route is only appended to session id when using ha profile

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9211?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9211: ------------------------------- > Route is only appended to session id when using ha profile > ---------------------------------------------------------- > > Key: WFLY-9211 > URL: https://issues.jboss.org/browse/WFLY-9211 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 11.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > instance-id only works for profiles with ha: > {code:java} > <subsystem xmlns="urn:jboss:domain:undertow:4.0" instance-id="node1"> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2207) Use of AUTH does result in a SecurityException if another client does not use AUTH

by Mirko Streckenbach (JIRA)

[ https://issues.jboss.org/browse/JGRP-2207?page=com.atlassian.jira.plugin.... ] Mirko Streckenbach commented on JGRP-2207: ------------------------------------------ [~belaban] Your example has AUTH configured on both stacks which works fine. My example omits AUTH on the second stack, so only the coordinator has AUTH. In that case it does not work regardless of authenticate_coord (our original code has that set, I shortened it for the example). IMHO the following code is responsible: {code} if(gms_hdr != null && needsAuthentication(gms_hdr)) { AuthHeader auth_hdr=msg.getHeader(id); if(auth_hdr == null) throw new IllegalStateException(String.format("found %s from %s but no AUTH header", gms_hdr, msg.src())); if(!handleAuthHeader(gms_hdr, auth_hdr, msg)) // authentication failed return null; // don't pass up } {code} If this runs on the coordinator and the second stack tries to join an IllegalStateException is thrown and that results in the package dropped, without a rejection being sent. My suggestion would be to change it to something like (untested): {code} if(gms_hdr != null && needsAuthentication(gms_hdr)) { AuthHeader auth_hdr=msg.getHeader(id); if(auth_hdr == null) { log.warn(...) sendRejectionMessage(gms_hdr.getType(), msg.getSrc(), "authentication failed"); return null; } if(!handleAuthHeader(gms_hdr, auth_hdr, msg)) // authentication failed return null; // don't pass up } {code} However, this might have other side effects well beyond my understanding of JGroups We are going to create distributed locks on top of the example, so a rogue cluster does not sound too good for us. Thanks for your hints regarding AUTH and encryption. This is not something we plan on using right now, but might be a topic for the future. > Use of AUTH does result in a SecurityException if another client does not use AUTH > ---------------------------------------------------------------------------------- > > Key: JGRP-2207 > URL: https://issues.jboss.org/browse/JGRP-2207 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.4 > Reporter: Mirko Streckenbach > Assignee: Bela Ban > Fix For: 4.0.5 > > Attachments: JGroupsAuthExample.java, JGroupsAuthExample.java > > > If there are two members in a cluster, one with AUTH configured and started first, so it can become the coordinator and a second without AUTH, the documentation implies that the second should receive a SecurityException. Instead, it creates it's own cluster. This works as expected if the second member uses AUTH, but has a different SecurityToken. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3054) (7.1.0) Connection timeout CLI issue on HTTPS, if more cli clients are used in a loop.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3054?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-3054: -------------------------------------- > (7.1.0) Connection timeout CLI issue on HTTPS, if more cli clients are used in a loop. > -------------------------------------------------------------------------------------- > > Key: WFCORE-3054 > URL: https://issues.jboss.org/browse/WFCORE-3054 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Critical > > *Description of problem:* > Connection timeout CLI issue on HTTPS, if more cli clients are used in a loop. > *Steps to Reproduce:* > # configure https > # loop, more clients in parralel: > #* ./jboss-cli.sh -c ":read-attribute(name=server-state)" -Djavax.net.ssl.trustStore=... -Djavax.net.ssl.trustStorePassword=... > *How reproducible:* > Intermittently > *Actual results:* > Thread dump is attached -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 August 2017