December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14142) Upgrade Google guava from 25.0-jre to 30.0-jre

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFLY-14142?page=com.atlassian.jira.plugi... ] Boris Unckel updated WFLY-14142: -------------------------------- Description: Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. [Release Notes|https://github.com/google/guava/releases/tag/v30.0] [Release-Diff|https://github.com/google/guava/compare/v25.0...v30.0] The update is justified due to ForkJoin Security Manager improvement: [Issue 3784|https://github.com/google/guava/issues/3784] [Commit|https://github.com/google/guava/commit/6e0c5b5d50a3e457ae0d787f7c9...] was: Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. [Release Notes|https://github.com/google/guava/releases/tag/v30.0] The update is justified due to ForkJoin Security Manager improvement: [Issue 3784|https://github.com/google/guava/issues/3784] [Commit|https://github.com/google/guava/commit/6e0c5b5d50a3e457ae0d787f7c9...] > Upgrade Google guava from 25.0-jre to 30.0-jre > ---------------------------------------------- > > Key: WFLY-14142 > URL: https://issues.redhat.com/browse/WFLY-14142 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch, JMS, Test Suite > Reporter: Boris Unckel > Assignee: Cheng Fang > Priority: Major > Attachments: 2020-12-01_04after_guava_build.txt > > > Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. > [Release Notes|https://github.com/google/guava/releases/tag/v30.0] > [Release-Diff|https://github.com/google/guava/compare/v25.0...v30.0] > The update is justified due to ForkJoin Security Manager improvement: [Issue 3784|https://github.com/google/guava/issues/3784] [Commit|https://github.com/google/guava/commit/6e0c5b5d50a3e457ae0d787f7c9...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5203) Update Google guava to 30.0-jre

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFCORE-5203?page=com.atlassian.jira.plug... ] Boris Unckel updated WFCORE-5203: --------------------------------- Description: Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. [Release Notes|https://github.com/google/guava/releases/tag/v30.0] [Release-Diff|https://github.com/google/guava/compare/v25.0...v30.0] was: Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. [Release Notes|https://github.com/google/guava/releases/tag/v30.0] > Update Google guava to 30.0-jre > ------------------------------- > > Key: WFCORE-5203 > URL: https://issues.redhat.com/browse/WFCORE-5203 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Affects Versions: 14.0.0.Beta2 > Reporter: Boris Unckel > Priority: Major > > Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. > [Release Notes|https://github.com/google/guava/releases/tag/v30.0] > [Release-Diff|https://github.com/google/guava/compare/v25.0...v30.0] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14179) Update commons-lang3 3.11

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFLY-14179?page=com.atlassian.jira.plugi... ] Boris Unckel updated WFLY-14179: -------------------------------- Description: Update [Apache commons-lang3 3.11|https://mvnrepository.com/artifact/org.apache.commons/commons-lang3/...] [Release Notes|https://commons.apache.org/proper/commons-lang/changes-report.html#...] [Release-Diff|https://github.com/apache/commons-lang/compare/rel/commons-l...] was: Update [Apache commons-lang3 3.11|https://mvnrepository.com/artifact/org.apache.commons/commons-lang3/...] [Release Notes|https://commons.apache.org/proper/commons-lang/changes-report.html#...] > Update commons-lang3 3.11 > ------------------------- > > Key: WFLY-14179 > URL: https://issues.redhat.com/browse/WFLY-14179 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Affects Versions: 22.0.0.Alpha1 > Reporter: Boris Unckel > Assignee: Brian Stansberry > Priority: Major > > Update [Apache commons-lang3 3.11|https://mvnrepository.com/artifact/org.apache.commons/commons-lang3/...] > [Release Notes|https://commons.apache.org/proper/commons-lang/changes-report.html#...] > [Release-Diff|https://github.com/apache/commons-lang/compare/rel/commons-l...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14176) Update commons-cli to 1.4

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFLY-14176?page=com.atlassian.jira.plugi... ] Boris Unckel updated WFLY-14176: -------------------------------- Description: Update [Commons-CLI 1.4|https://mvnrepository.com/artifact/commons-cli/commons-cli/1.4] [Release Notes|https://commons.apache.org/proper/commons-cli/release_1_4.html] [Release-Diff|https://github.com/apache/commons-cli/compare/cli-1.3.1...cl...] was: Update [Commons-CLI 1.4|https://mvnrepository.com/artifact/commons-cli/commons-cli/1.4] [Release Notes|https://commons.apache.org/proper/commons-cli/release_1_4.html] > Update commons-cli to 1.4 > ------------------------- > > Key: WFLY-14176 > URL: https://issues.redhat.com/browse/WFLY-14176 > Project: WildFly > Issue Type: Component Upgrade > Components: CLI > Affects Versions: 22.0.0.Alpha1 > Reporter: Boris Unckel > Assignee: Jean Francois Denise > Priority: Major > > Update [Commons-CLI 1.4|https://mvnrepository.com/artifact/commons-cli/commons-cli/1.4] > [Release Notes|https://commons.apache.org/proper/commons-cli/release_1_4.html] > [Release-Diff|https://github.com/apache/commons-cli/compare/cli-1.3.1...cl...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5890) DMN DT Analysis 2NF detection edge-case

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5890?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5890: ----------------------------------- Story Points: 3 (was: 8) Sprint: 2020 Week 49-51 (from Nov 30) > DMN DT Analysis 2NF detection edge-case > --------------------------------------- > > Key: DROOLS-5890 > URL: https://issues.redhat.com/browse/DROOLS-5890 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > Detect edge case of 2NF violation such as > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5890) DMN DT Analysis 2NF detection edge-case

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5890?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5890: ----------------------------------- Description: Detect edge case of 2NF violation such as !screenshot-1.png|thumbnail! was: In a table such as !screenshot-1.png|thumbnail! rules 4,5,6 and rules 7,8 should be candidate of 2NF violations. > DMN DT Analysis 2NF detection edge-case > --------------------------------------- > > Key: DROOLS-5890 > URL: https://issues.redhat.com/browse/DROOLS-5890 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > Detect edge case of 2NF violation such as > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5890) DMN DT Analysis 2NF detection edge-case

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5890?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5890: ----------------------------------- Attachment: screenshot-1.png > DMN DT Analysis 2NF detection edge-case > --------------------------------------- > > Key: DROOLS-5890 > URL: https://issues.redhat.com/browse/DROOLS-5890 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > In a table such as > !screenshot-1.png|thumbnail! > rules 4,5,6 and rules 7,8 should be candidate of 2NF violations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5890) DMN DT Analysis 2NF detection edge-case

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5890: -------------------------------------- Summary: DMN DT Analysis 2NF detection edge-case Key: DROOLS-5890 URL: https://issues.redhat.com/browse/DROOLS-5890 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: screenshot-1.png In a table such as !screenshot-1.png|thumbnail! rules 4,5,6 and rules 7,8 should be candidate of 2NF violations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2522) FD_ALL2 throws NPE

by Bela Ban (Jira)

Bela Ban created JGRP-2522: ------------------------------ Summary: FD_ALL2 throws NPE Key: JGRP-2522 URL: https://issues.redhat.com/browse/JGRP-2522 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.2, 4.2.11 This is in 4.x: {noformat} Exception in thread "jgroups-28,TEST4,192.168.123.100:Reciever-18" java.lang.NullPointerException at org.jgroups.protocols.FD_ALL2.lambda$new$0(FD_ALL2.java:83) at org.jgroups.util.MessageBatch.replaceIf(MessageBatch.java:220) at org.jgroups.protocols.FD_ALL2.up(FD_ALL2.java:186) at org.jgroups.stack.Protocol.up(Protocol.java:372) at org.jgroups.stack.Protocol.up(Protocol.java:372) at org.jgroups.stack.Protocol.up(Protocol.java:372) at org.jgroups.protocols.TP.passBatchUp(TP.java:1274) at org.jgroups.util.SubmitToThreadPool$BatchHandler.passBatchUp(SubmitToThreadPool.java:140) at org.jgroups.util.SubmitToThreadPool$BatchHandler.run(SubmitToThreadPool.java:136) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2521) FD_SOCK2

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2521?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2521: --------------------------- Description: FD_SOCK is quite old and hasn't been given a lot of maintenance love over the last two decades (2001!). The code is quite complicated/brittle and could use some simplification. The major enhancement is to use a fixed port, so we can scrap the code which maintains the cache of IP addresses:ports and UUIDs. This requires a poor man's state transfer of this cache to new members, plus update messages whenever a new member starts. Using a fixed port allows us to reuse the UUID/IP-address cache, which already exists in the transport. When a view change is received, a member simply determines the peer to which to connect to by grabbing the peer's IP address from the transport cache, and connecting to it at {{port}}. We probably need a port range, too. was: FD_SOCK is quite old and hasn't been given a lot of maintenance love over the last two decades (2001!). The code is quite complicated/brittle and could use some simplification. The major enhancement is to use a fixed port, so we can scrap the code which maintains the cache of IP addresses:ports and UUIDs. This requires a poor man's state transfer of this cache to new members, plus update messages whenever a new member starts. Using a fixed port allows us to reuse the UUID/IP-address cache, which already exists in the transport. When a view change is received, a member simply determines the peer to which to connect to by grabbing the peer's IP address from the transport cache, and connecting to it at {{port}}. We probably need a port range. > FD_SOCK2 > -------- > > Key: JGRP-2521 > URL: https://issues.redhat.com/browse/JGRP-2521 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.2 > > > FD_SOCK is quite old and hasn't been given a lot of maintenance love over the last two decades (2001!). > The code is quite complicated/brittle and could use some simplification. > The major enhancement is to use a fixed port, so we can scrap the code which maintains the cache of IP addresses:ports and UUIDs. This requires a poor man's state transfer of this cache to new members, plus update messages whenever a new member starts. > Using a fixed port allows us to reuse the UUID/IP-address cache, which already exists in the transport. When a view change is received, a member simply determines the peer to which to connect to by grabbing the peer's IP address from the transport cache, and connecting to it at {{port}}. We probably need a port range, too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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