[JBoss JIRA] (WFCORE-4842) Add support for TLSv1.3 using the OpenSSL TLS provider
by Ken Wills (Jira)
[ https://issues.redhat.com/browse/WFCORE-4842?page=com.atlassian.jira.plug... ]
Ken Wills commented on WFCORE-4842:
-----------------------------------
[~fjuma] Looks like RHEL has the optional package openssl11 now which installs:
{noformat}
-rwxr-xr-x 1 root root 370584 Dec 10 2019 /usr/lib64/libssl3.so
lrwxrwxrwx 1 root root 16 Sep 20 2019 /usr/lib64/libssl.so.10 -> libssl.so.1.0.2k
-rwxr-xr-x 1 root root 470376 Aug 8 2019 /usr/lib64/libssl.so.1.0.2k
lrwxrwxrwx 1 root root 16 Jul 20 11:43 /usr/lib64/libssl.so.1.1 -> libssl.so.1.1.1c
-rwxr-xr-x 1 root root 603520 May 13 04:30 /usr/lib64/libssl.so.1.1.1c
{noformat}
We can certainly install that on agents.
I'll have to look at the windows versions, they probably need to be updated manually.
> Add support for TLSv1.3 using the OpenSSL TLS provider
> ------------------------------------------------------
>
> Key: WFCORE-4842
> URL: https://issues.redhat.com/browse/WFCORE-4842
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Tristan Tarrant
> Assignee: Farah Juma
> Priority: Major
>
> The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-13575) Remove all hard coded references to Artemis default values
by Michal Petrov (Jira)
[ https://issues.redhat.com/browse/WFLY-13575?page=com.atlassian.jira.plugi... ]
Michal Petrov commented on WFLY-13575:
--------------------------------------
Well now I'm confused. The test is detecting configuration changes (that is WidlFly configuration is different from Artemis configuration) yet you said that those are "not an issue". Should I specifically exclude the attributes I've listed? Or is the test supposed to be checking against some "Artemis snapshot" and not WildFly?
> 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, 9 months
[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13680?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13680:
---------------------------------------------
I removed CLI component and added Metrics. CLI is not involved in this scenario.
> 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, 9 months
[JBoss JIRA] (WFLY-13680) Generated metrics have duplicate labels
by Michal Petrov (Jira)
[ https://issues.redhat.com/browse/WFLY-13680?page=com.atlassian.jira.plugi... ]
Michal Petrov commented on WFLY-13680:
--------------------------------------
In the report there is
{code:java}
base_gc_total{name="Copy1"} 17.0
base_gc_total{name="MarkSweepCompact1"} 0.0{code}
This doesn't look like a problem with the metrics but rather with the tool reading them.
> Generated metrics have duplicate labels
> ---------------------------------------
>
> Key: WFLY-13680
> URL: https://issues.redhat.com/browse/WFLY-13680
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Reporter: Ivona Skorjanc
> Assignee: Jean Francois Denise
> 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, 9 months
[JBoss JIRA] (WFLY-12681) Provide a 'microprofile-platform' Galleon layer
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-12681?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-12681:
----------------------------------
Affects Version/s: 20.0.1.Final
20.0.0.Final
> Provide a 'microprofile-platform' Galleon layer
> -----------------------------------------------
>
> Key: WFLY-12681
> URL: https://issues.redhat.com/browse/WFLY-12681
> Project: WildFly
> Issue Type: Feature Request
> Components: Build System, MP Config, MP Fault Tolerance, MP Health, MP JWT, MP Metrics, MP OpenAPI, MP OpenTracing
> Affects Versions: 20.0.0.Final, 20.0.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Labels: Microprofile
>
> We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774.
> With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months