August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-937) PSI Clusters are getting pods on evicted State

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-937?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-937: -------------------------------- Sprint: Kiali Sprint #27 > PSI Clusters are getting pods on evicted State > ---------------------------------------------- > > Key: SWSQE-937 > URL: https://issues.jboss.org/browse/SWSQE-937 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > Attachments: ps1.png, ps2.png, psi-kqe1.png > > > KQE1 as an example is getting pods on the evicted state (service mesh and non service mesh related). > I have seen this problem on the kqe-mt which has more workers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2274) ASYM_ENCRYPT: deprecate sign_msgs

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2274?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2274: -------------------------------- [~nsawadsky] You're much more of an expert than me, but I always assumed that even a flipped bit in an encrypted message would lead to an error when decrypting it. Apparently that is not the case? Is there a need for an additional protocol INTEGRITY (or CHECKSUM) that performs integrity checking? > ASYM_ENCRYPT: deprecate sign_msgs > --------------------------------- > > Key: JGRP-2274 > URL: https://issues.jboss.org/browse/JGRP-2274 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.12 > > > In {{ASYM_ENCRYPT}}, signing messages means that the checksum of an encrypted message is computed and used together with the secret key of the sender to sign the message. On the receiver side, the public key of the sender is used to validate the signature. > However, this is redundant, as decryption of a message will fail if the contents have been changed. > If needed, signing of messages can be done in a separate protocol. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-937) PSI Clusters are getting pods on evicted State

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-937?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-937: ------------------------------------------ Attachment: psi-kqe1.png > PSI Clusters are getting pods on evicted State > ---------------------------------------------- > > Key: SWSQE-937 > URL: https://issues.jboss.org/browse/SWSQE-937 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > Attachments: ps1.png, ps2.png, psi-kqe1.png > > > KQE1 as an example is getting pods on the evicted state (service mesh and non service mesh related). > I have seen this problem on the kqe-mt which has more workers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-937) PSI Clusters are getting pods on evicted State

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-937: --------------------------------------------- Summary: PSI Clusters are getting pods on evicted State Key: SWSQE-937 URL: https://issues.jboss.org/browse/SWSQE-937 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Filip Brychta Attachments: ps1.png, ps2.png KQE1 as an example is getting pods on the evicted state (service mesh and non service mesh related). I have seen this problem on the kqe-mt which has more workers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11963?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11963: --------------------------------------- I've changed it to bug as it's currently referencing to capability in jberet subsystem which is odd and does not make sense. > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.jboss.org/browse/WFLY-11963 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11963?page=com.atlassian.jira.plugin... ] Miroslav Novak updated WFLY-11963: ---------------------------------- Issue Type: Bug (was: Enhancement) > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.jboss.org/browse/WFLY-11963 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4426) Remove version.org.kie property from droolsjbpm-build-bootstrap project

by Marek Novotny (Jira)

[ https://issues.jboss.org/browse/DROOLS-4426?page=com.atlassian.jira.plugi... ] Marek Novotny commented on DROOLS-4426: --------------------------------------- okay, you can you are the reporter ;) > Remove version.org.kie property from droolsjbpm-build-bootstrap project > ----------------------------------------------------------------------- > > Key: DROOLS-4426 > URL: https://issues.jboss.org/browse/DROOLS-4426 > Project: Drools > Issue Type: Bug > Affects Versions: 7.24.0.Final > Reporter: Enrique Mingorance Cano > Assignee: Mario Fusco > Priority: Major > > The property "version.org.kie" is already defined in the kie-parent project and it should removed from droolsjbpm-build-bootstrap project > https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/bc4de568cac27... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-178) [Galleon] Script fails when JGROUPS_CLUSTER_PASSWORD is set by template

by Nikoleta Ziakova (Jira)

Nikoleta Ziakova created WFWIP-178: -------------------------------------- Summary: [Galleon] Script fails when JGROUPS_CLUSTER_PASSWORD is set by template Key: WFWIP-178 URL: https://issues.jboss.org/browse/WFWIP-178 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Nikoleta Ziakova Assignee: Jean Francois Denise Steps to reproduce: # Provision server without jgroups subsystem, e.g. https://github.com/nziakova/jboss-eap-quickstarts/tree/with_galleon_dir/k... # Use [template|https://github.com/jboss-container-images/jboss-eap-7-openshift-...] to deploy the application The template sets default {{JGROUPS_CLUSTER_PASSWORD}} which causes the scripts fail: {code} ERROR "Cannot configure the jgroups authentication. The jgroups subsystem is not present in the server configuration file." {code} It must be decided whether it is a bug in scripts or templates. Updating the templates would cause backwards compatibility issues. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12396) Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFLY-12396?page=com.atlassian.jira.plugin... ] Diana Vilkolakova deleted WFLY-12396: ------------------------------------- > Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12396 > URL: https://issues.jboss.org/browse/WFLY-12396 > Project: WildFly > Issue Type: Sub-task > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12396) Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFLY-12396?page=com.atlassian.jira.plugin... ] Diana Vilkolakova closed WFLY-12396. ------------------------------------ Resolution: Done > Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12396 > URL: https://issues.jboss.org/browse/WFLY-12396 > Project: WildFly > Issue Type: Sub-task > Components: EE, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 2019