[Red Hat JIRA] (JGRP-2434) Parse epoch TShark field
by Diego Lovison (Jira)
[ https://issues.redhat.com/browse/JGRP-2434?page=com.atlassian.jira.plugin... ]
Diego Lovison updated JGRP-2434:
--------------------------------
Summary: Parse epoch TShark field (was: Support multiple TShark fields parser)
> Parse epoch TShark field
> ------------------------
>
> Key: JGRP-2434
> URL: https://issues.redhat.com/browse/JGRP-2434
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.0.Alpha3
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Major
>
> In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}}
> Changes
> * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}}
> * {{Util::parse}} is used in GossipRouter
> Why have a diff parser
> * Prevent changing production code
> * Easy to create/add more fields related only with TShark
> * It reuse the {{Util::parse}}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (JGRP-2434) Parse epoch TShark field
by Diego Lovison (Jira)
[ https://issues.redhat.com/browse/JGRP-2434?page=com.atlassian.jira.plugin... ]
Diego Lovison updated JGRP-2434:
--------------------------------
Description: Parse epoch TShark field (was: In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}}
Changes
* Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}}
* {{Util::parse}} is used in GossipRouter
Why have a diff parser
* Prevent changing production code
* Easy to create/add more fields related only with TShark
* It reuse the {{Util::parse}})
> Parse epoch TShark field
> ------------------------
>
> Key: JGRP-2434
> URL: https://issues.redhat.com/browse/JGRP-2434
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.0.Alpha3
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Major
>
> Parse epoch TShark field
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFLY-11933?page=com.atlassian.jira.plugi... ]
Jeff Mesnil commented on WFLY-11933:
------------------------------------
in WFLY-14108, I've changed the code to log at debug the error when RBAC prevents to read metrics. This prevents any sensitive information to be bypassed
> Error when accessing metrics with RBAC enabled
> ----------------------------------------------
>
> Key: WFLY-11933
> URL: https://issues.redhat.com/browse/WFLY-11933
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Metrics
> Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final, 21.0.0.Final
> Reporter: Claudio Weiler
> Assignee: Jeff Mesnil
> Priority: Major
>
> Accordingly to https://docs.wildfly.org/17/Admin_Guide.html#http-endpoint-2 and https://wildscribe.github.io/WildFly/17.0/subsystem/microprofile-metrics-..., access to metrics endpoint is controlled by the security-enabled attribute.
> When this attribute is set to false, there is an Exception when metrics are accessed. By default, this attribute is set to false on standalone.xml config.
> Please, refer to steps to reproduce. This error occurs only when RBAC are enabled.
> When RBAC is enabled for management in Wildfly, metrics throws exception:
> java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS"),
> ("statistics" => "pool")
> ]: "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\"),
> (\"statistics\" => \"pool\")
> ]' not found".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months