October 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13744) Improvements on Galleon layers community documentation

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-13744?page=com.atlassian.jira.plugi... ] Jean Francois Denise reassigned WFLY-13744: ------------------------------------------- Assignee: Jean Francois Denise (was: Yeray Borges Santana) > Improvements on Galleon layers community documentation > ------------------------------------------------------ > > Key: WFLY-13744 > URL: https://issues.redhat.com/browse/WFLY-13744 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Yeray Borges Santana > Assignee: Jean Francois Denise > Priority: Major > > We could make some improvements on the WildFly community documentation about the Galleon layers: > * Somehow facilitate the identification of what contains each layer. > * Describe in this Galleon layers section a short introduction about the different available options to generate a trimmed server > * Links about examples > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5685) ClearActivationGroup command changed its behaviour

by Karel Suta (Jira)

Karel Suta created DROOLS-5685: ---------------------------------- Summary: ClearActivationGroup command changed its behaviour Key: DROOLS-5685 URL: https://issues.redhat.com/browse/DROOLS-5685 Project: Drools Issue Type: Bug Components: core engine, kie server Affects Versions: 7.44.0.Final Reporter: Karel Suta Assignee: Matteo Mortari ClearActivationGroupCommand command in Kie server changed its behaviour, right now it doesn't seem to remove the activation group. This issue is caused by https://github.com/kiegroup/drools/pull/3125 , when I revert the commit then ClearActivationGroupCommand works again as before. Can be reproduced using Kie server integration test [ActivationGroupIntegrationTest.testClearActivationGroup()|https://github....]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13922) Upgrade RESTEasy to 3.13.2.Final

by Alessio Soldano (Jira)

[ https://issues.redhat.com/browse/WFLY-13922?page=com.atlassian.jira.plugi... ] Alessio Soldano updated WFLY-13922: ----------------------------------- Priority: Critical (was: Major) > Upgrade RESTEasy to 3.13.2.Final > -------------------------------- > > Key: WFLY-13922 > URL: https://issues.redhat.com/browse/WFLY-13922 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Critical > Labels: downstream_dependency > Fix For: 21.0.0.Final > > > Upgrade from 3.11.2.Final to 3.12.0.Final > Diff: https://github.com/resteasy/Resteasy/compare/3.13.1.Final...3.13.2.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2504) Poor throughput over high latency TCP connection when recv_buf_size is configured

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2504?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2504: -------------------------------- I'll reply in detail later, but I know what the problem is: I thought I was using {{TCP.recv_buf_size}} (which *is* set correctly), but instead I used {{TCP.TcpServer.recv_buf_size}} which is set *after* {{bind()}}. I'll fix this today. > Poor throughput over high latency TCP connection when recv_buf_size is configured > --------------------------------------------------------------------------------- > > Key: JGRP-2504 > URL: https://issues.redhat.com/browse/JGRP-2504 > Project: JGroups > Issue Type: Bug > Affects Versions: 5.0.0.Final > Reporter: Andrew Skalski > Assignee: Bela Ban > Priority: Minor > Fix For: 5.1 > > Attachments: SpeedTest.java, bla5.java, bla6.java, bla7.java, delay-ip.sh > > > I recently finished troubleshooting a unidirectional throughput bottleneck involving a JGroups application (Infinispan) communicating over a high-latency (~45 milliseconds) TCP connection. > The root cause was JGroups improperly configuring the receive/send buffers on the listening socket. According to the tcp(7) man page: > {code:java} > On individual connections, the socket buffer size must be set prior to > the listen(2) or connect(2) calls in order to have it take effect. > {code} > However, JGroups does not set the buffer size on the listening side until after accept(). > The result is poor throughput when sending data from client (connecting side) to server (listening side.) Because the issue is a too-small TCP receive window, throughput is ultimately latency-bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13922) Upgrade RESTEasy to 3.13.2.Final

by Alessio Soldano (Jira)

[ https://issues.redhat.com/browse/WFLY-13922?page=com.atlassian.jira.plugi... ] Alessio Soldano updated WFLY-13922: ----------------------------------- Fix Version/s: 21.0.0.Final (was: 21.0.0.Beta1) > Upgrade RESTEasy to 3.13.2.Final > -------------------------------- > > Key: WFLY-13922 > URL: https://issues.redhat.com/browse/WFLY-13922 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Final > > > Upgrade from 3.11.2.Final to 3.12.0.Final > Diff: https://github.com/resteasy/Resteasy/compare/3.13.1.Final...3.13.2.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13923) Upgrade Jackson to 2.10.5

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-13923: -------------------------------------- Summary: Upgrade Jackson to 2.10.5 Key: WFLY-13923 URL: https://issues.redhat.com/browse/WFLY-13923 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 21.0.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5684: ----------------------------------- Description: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority as in the following example: !screenshot-2.png|thumbnail! which was implemented with [DROOLS-3785]. ( ref: https://youtu.be/eQRDc6fq2yw?t=1293 ) Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png|thumbnail! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} was: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority as in the following example: !screenshot-2.png|thumbnail! which was implemented with [DROOLS-3785]. Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png|thumbnail! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} > DMN DT Analysis Misleading rule definition refinements > ------------------------------------------------------ > > Key: DROOLS-5684 > URL: https://issues.redhat.com/browse/DROOLS-5684 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > The original definition is: > bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority > as in the following example: > !screenshot-2.png|thumbnail! > which was implemented with [DROOLS-3785]. > ( ref: https://youtu.be/eQRDc6fq2yw?t=1293 ) > Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] > However, a table such as the below would inadvertently still report misleading rules: > !screenshot-1.png|thumbnail! > So the new definition is refined to: > {quote}P tables can be “misleading” when: > * rule contains hyphen input entry (“irrelevant”) > * and output is not lowest priority > * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5684: ----------------------------------- Attachment: screenshot-2.png > DMN DT Analysis Misleading rule definition refinements > ------------------------------------------------------ > > Key: DROOLS-5684 > URL: https://issues.redhat.com/browse/DROOLS-5684 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > The original definition is: > bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority > which was implemented with [DROOLS-3785]. > Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] > However, a table such as the below would inadvertently still report misleading rules: > !screenshot-1.png|thumbnail! > So the new definition is refined to: > {quote}P tables can be “misleading” when: > * rule contains hyphen input entry (“irrelevant”) > * and output is not lowest priority > * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5684: ----------------------------------- Description: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority as in the following example: !screenshot-2.png|thumbnail! which was implemented with [DROOLS-3785]. Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png|thumbnail! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} was: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority which was implemented with [DROOLS-3785]. Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png|thumbnail! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} > DMN DT Analysis Misleading rule definition refinements > ------------------------------------------------------ > > Key: DROOLS-5684 > URL: https://issues.redhat.com/browse/DROOLS-5684 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png > > > The original definition is: > bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority > as in the following example: > !screenshot-2.png|thumbnail! > which was implemented with [DROOLS-3785]. > Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] > However, a table such as the below would inadvertently still report misleading rules: > !screenshot-1.png|thumbnail! > So the new definition is refined to: > {quote}P tables can be “misleading” when: > * rule contains hyphen input entry (“irrelevant”) > * and output is not lowest priority > * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5684) DMN DT Analysis Misleading rule definition refinements

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5684?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5684: ----------------------------------- Description: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority which was implemented with [DROOLS-3785]. Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png|thumbnail! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} was: The original definition is: bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority which was implemented with [DROOLS-3785]. Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] However, a table such as the below would inadvertently still report misleading rules: !screenshot-1.png! So the new definition is refined to: {quote}P tables can be “misleading” when: * rule contains hyphen input entry (“irrelevant”) * and output is not lowest priority * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule {quote} > DMN DT Analysis Misleading rule definition refinements > ------------------------------------------------------ > > Key: DROOLS-5684 > URL: https://issues.redhat.com/browse/DROOLS-5684 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > The original definition is: > bq. P tables can be “misleading” when rule contains hyphen input entry (“irrelevant”) and output is not lowest priority > which was implemented with [DROOLS-3785]. > Further refinements checked to avoid duplicating "Misleading rule" reports when in fact the rules were already reported as "Masked", with: [DROOLS-5368] > However, a table such as the below would inadvertently still report misleading rules: > !screenshot-1.png|thumbnail! > So the new definition is refined to: > {quote}P tables can be “misleading” when: > * rule contains hyphen input entry (“irrelevant”) > * and output is not lowest priority > * the hyphen in the misleading rule, correspond to a value (not an hyphen) in the mislead('d) rule > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2020