[JBoss JIRA] (WFLY-11256) Fix Undertow Metrics
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-11256:
----------------------------------
Summary: Fix Undertow Metrics
Key: WFLY-11256
URL: https://issues.jboss.org/browse/WFLY-11256
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 14.0.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Undertow metrics are relevant only when /subsystem=undertow's statistics-enabled is true.
When that it not the case (and metrics can not be computer) the metrics' read handler should not return a meaningless value (e.g. 0) as it already specifies an undefined metric value in the metrics' attribute definition.
That change and WFCORE-4190 will prevent exposing Undertow metrics when they do not report actual metric from Undertow underlying runtime.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3193:
-------------------------------------
[~tirelli] [~danielezonca] Would this be valid:
!Screen Shot 2018-10-30 at 10.50.55 AM.png|thumbnail!
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png
>
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JGRP-2305) Get rid of need for java.net.preferIPv4Stack
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2305?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2305:
---------------------------
Description:
New address picking scheme:
* First we detect which addresses are available: IPv4 and/or IPv6 (dual-stack if both)
* When we encounter an IPv4 address:
** If dual-stack or IPv4 stack: use it
** If IPv6-only stack: use it unless it is a class D (multicast) address: then convert it to an IPv6-mapped address
* When we encounter an IPv6 address:
** If dual-stack or IPv6-only stack: use it
** Else: throw an exception (IPv6 address in an IPv4-only stack)
was:
New address picking scheme:
* If all addresses in the config file are IPv4: use IPv4 addresses if available, else use IPv6 addresses
* If all addresses are IPv6: use IPv6
* If there is one IPv6 address: use IPv6
* If we have an IPv4 address, but the stack is not dual (but just IPv6) -> use IPv6-mapped addresses
Document the exact semantics
> Get rid of need for java.net.preferIPv4Stack
> --------------------------------------------
>
> Key: JGRP-2305
> URL: https://issues.jboss.org/browse/JGRP-2305
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16
>
>
> New address picking scheme:
> * First we detect which addresses are available: IPv4 and/or IPv6 (dual-stack if both)
> * When we encounter an IPv4 address:
> ** If dual-stack or IPv4 stack: use it
> ** If IPv6-only stack: use it unless it is a class D (multicast) address: then convert it to an IPv6-mapped address
> * When we encounter an IPv6 address:
> ** If dual-stack or IPv6-only stack: use it
> ** Else: throw an exception (IPv6 address in an IPv4-only stack)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4191) Fix IO Metrics Registration
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4191?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4191:
--------------------------------
Description:
* shutdown-requested is a (boolean) runtime read-only attribute, not a metric
* the other attributes are correctly registered as metrics. However their definition should not specify "undefined metric value" as their values can always be computed.
was:
shutdown-requested is a (boolean) runtime read-only attribute, not a metric
> Fix IO Metrics Registration
> ---------------------------
>
> Key: WFCORE-4191
> URL: https://issues.jboss.org/browse/WFCORE-4191
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> * shutdown-requested is a (boolean) runtime read-only attribute, not a metric
> * the other attributes are correctly registered as metrics. However their definition should not specify "undefined metric value" as their values can always be computed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3193:
---------------------------------------
No, the user can give labels to instances (e.g. the "seller" label for the Company instance) or to attributes (e.g., a "cs" label to a credit score attribute on a Person instance). Each row is a scenario/test, so having numbered rows make sense.
[~danielezonca] any concerns/thoughts?
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3193:
-------------------------------------
[~tirelli] Thanks, good to know - no numbering of instances. Is there any concept of column number/position (like a spreadsheet) that needs to be worked into the UI ?
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month