July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2491) Reduce use of synchronized

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2491?page=com.atlassian.jira.plugin... ] Bela Ban closed JGRP-2491. -------------------------- Resolution: Won't Fix This will be fixed by the Loom project (replacing synchronized with ReentrantLock intrinsically) > Reduce use of synchronized > -------------------------- > > Key: JGRP-2491 > URL: https://issues.redhat.com/browse/JGRP-2491 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0.0.Final > > > The synchronized keyword fares badly with virtual threads (project Loom). Contrary to {{java.util.concurrent.lock.Lock}}, {{synchronized}} can still block. This might change in the future, but for now, we should replace all uses of {{synchronized}} with {{Lock.lock()/unlock().}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

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

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2274?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2274: -------------------------------- [~nsawadsky] Perhaps support for this is enabled in more recent JDKs (I used 11)? > ASYM_ENCRYPT: deprecate sign_msgs > --------------------------------- > > Key: JGRP-2274 > URL: https://issues.redhat.com/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.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels

by Ivona Skorjanc (Jira)

[ https://issues.redhat.com/browse/WFLY-13680?page=com.atlassian.jira.plugi... ] Ivona Skorjanc commented on WFLY-13680: --------------------------------------- Thanks for the quick feedback > Generated metrics have duplicate labels > --------------------------------------- > > Key: WFLY-13680 > URL: https://issues.redhat.com/browse/WFLY-13680 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Ivona Skorjanc > Assignee: Jeff Mesnil > Priority: Major > Fix For: 19.0.0.Final > > Attachments: kc_metric.txt > > > We are using Keycloak which generates metrics using the jBoss CLI: [https://github.com/keycloak/keycloak-containers/blob/master/server/tools/...] > We want to use Telegraf (with the Prometheus input plugin) to read the generated metrics. However, we get the following error: > {{Error in plugin: error reading metrics for [http://localhost:9990/metrics]: reading text format failed: text format parsing error in line 34: second HELP line for metric name "base_gc_total"}} > The base_gc_total metric appears twice for some reason. See the full metrics output in the attachment. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5059) Upgrade bootable testsuite to use 2.0.0.Alpha6 maven plugin

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-5059: -------------------------------------------- Summary: Upgrade bootable testsuite to use 2.0.0.Alpha6 maven plugin Key: WFCORE-5059 URL: https://issues.redhat.com/browse/WFCORE-5059 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3485) Misleading failure-description for capabilities in domain

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFCORE-3485?page=com.atlassian.jira.plug... ] Moulali Shikalwadi commented on WFCORE-3485: -------------------------------------------- [~olukas], [~brian.stansberry] Is this issue still persist? Could you please add some steps to reproduce it. > Misleading failure-description for capabilities in domain > --------------------------------------------------------- > > Key: WFCORE-3485 > URL: https://issues.redhat.com/browse/WFCORE-3485 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 3.0.10.Final > Reporter: Ondrej Lukas > Priority: Minor > > In case when configuration in domain.xml tries to reference any capability from host.xml (or vice versa), but should not be able to reference it then it correctly fails, but there is failure-description which is misleading. > Start domain with default domain.xml and host.xml and run following CLI command and see: > {code} > /profile=full/subsystem=elytron/http-authentication-factory=some-factory:add(http-server-mechanism-factory=global,security-domain=ManagementDomain) > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.security-domain.ManagementDomain in context 'profile=full'; Possible registration points for this capability: > /host=master/subsystem=elytron/security-domain=* > /profile=*/subsystem=elytron/security-domain=*"}, > "rolled-back" => true > } > {code} > It should show only correct registration point {{/profile=\*/subsystem=elytron/security-domain=\*}}. It is misleading because ManagementDomain capability exists in {{/host=master/subsystem=elytron/security-domain=*}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13575) Remove all hard coded references to Artemis default values

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13575?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13575: ------------------------------------------ The goal is to check for changes between current Artemis default and wildFly configuration default when they are not different currently. Those values you found should be excluded for now > Remove all hard coded references to Artemis default values > ---------------------------------------------------------- > > Key: WFLY-13575 > URL: https://issues.redhat.com/browse/WFLY-13575 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 20.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Michal Petrov > Priority: Major > > There are still attributes that use Artemis default configuration valuues from FileConfiguration for example. > Remove those values so that they are not updated behind the scene and add a test to know when our default values don't align with Artemis ones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13631) MicroProfile-Health: HealthChecks from WARs within EARs cannot be found

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13631?page=com.atlassian.jira.plugi... ] Jeff Mesnil resolved WFLY-13631. -------------------------------- Resolution: Duplicate Issue Reported issue is tracked by WFLY-12835 > MicroProfile-Health: HealthChecks from WARs within EARs cannot be found > ----------------------------------------------------------------------- > > Key: WFLY-13631 > URL: https://issues.redhat.com/browse/WFLY-13631 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 20.0.0.Final > Reporter: Jens Borrmann > Assignee: Jeff Mesnil > Priority: Major > > We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) > With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation > * Deploying as a WAR: Everything works fine > * Deploying as an EAR (containing the WAR) the following information is displayed: > {"status":"UP","checks":[\{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}]} > Remarks: > * Using the new and not deprecated /health/ready does not change anything > * Using OpenLiberty everything works fine -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3792) org.jboss.remoting module should be private

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFCORE-3792?page=com.atlassian.jira.plug... ] Moulali Shikalwadi commented on WFCORE-3792: -------------------------------------------- HI [~bmaxwell], Is this issue still persists? Could you please add some steps to reproduce it. > org.jboss.remoting module should be private > ------------------------------------------- > > Key: WFCORE-3792 > URL: https://issues.redhat.com/browse/WFCORE-3792 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 5.0.0.Alpha4 > Reporter: Brad Maxwell > Priority: Major > > org.jboss.remoting module should be private > /core-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/remoting/main/module.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13680?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-13680: ------------------------------------ I checked that WildFly 19 that upgraded the smallrye-metrics component (in charge of exporting the metrics) had fixed this issue in WFLY-13022 > Generated metrics have duplicate labels > --------------------------------------- > > Key: WFLY-13680 > URL: https://issues.redhat.com/browse/WFLY-13680 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Ivona Skorjanc > Assignee: Jeff Mesnil > Priority: Major > Attachments: kc_metric.txt > > > We are using Keycloak which generates metrics using the jBoss CLI: [https://github.com/keycloak/keycloak-containers/blob/master/server/tools/...] > We want to use Telegraf (with the Prometheus input plugin) to read the generated metrics. However, we get the following error: > {{Error in plugin: error reading metrics for [http://localhost:9990/metrics]: reading text format failed: text format parsing error in line 34: second HELP line for metric name "base_gc_total"}} > The base_gc_total metric appears twice for some reason. See the full metrics output in the attachment. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13680?page=com.atlassian.jira.plugi... ] Jeff Mesnil resolved WFLY-13680. -------------------------------- Fix Version/s: 19.0.0.Final Resolution: Done > Generated metrics have duplicate labels > --------------------------------------- > > Key: WFLY-13680 > URL: https://issues.redhat.com/browse/WFLY-13680 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Ivona Skorjanc > Assignee: Jeff Mesnil > Priority: Major > Fix For: 19.0.0.Final > > Attachments: kc_metric.txt > > > We are using Keycloak which generates metrics using the jBoss CLI: [https://github.com/keycloak/keycloak-containers/blob/master/server/tools/...] > We want to use Telegraf (with the Prometheus input plugin) to read the generated metrics. However, we get the following error: > {{Error in plugin: error reading metrics for [http://localhost:9990/metrics]: reading text format failed: text format parsing error in line 34: second HELP line for metric name "base_gc_total"}} > The base_gc_total metric appears twice for some reason. See the full metrics output in the attachment. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 12 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 July 2020