July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2478) Fibers: test performance versus regular threads

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2478?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2478: --------------------------- Description: Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. This requires a few code changes: * There's no need to pool fibers, see [1] for details * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} * In a future version, we could simply remove the 2 thread pools [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] was: Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. This requires a few code changes: * There's no need to pool fibers, see [1] for details * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} * In a future version, we could simply remove the 2 thread pool [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] > Fibers: test performance versus regular threads > ----------------------------------------------- > > Key: JGRP-2478 > URL: https://issues.redhat.com/browse/JGRP-2478 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. > This requires a few code changes: > * There's no need to pool fibers, see [1] for details > * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} > * In a future version, we could simply remove the 2 thread pools > [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2478) Fibers: test performance versus regular threads

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2478?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2478: --------------------------- Description: Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. This requires a few code changes: * There's no need to pool fibers, see [1] for details * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} * In a future version, we could simply remove the 2 thread pool [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] was: Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. This requires a few code changes: * There's no need to pool fibers, see [1] for details * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThradExecutor()}} * In a future version, we could simply remove the 2 thread pool [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] > Fibers: test performance versus regular threads > ----------------------------------------------- > > Key: JGRP-2478 > URL: https://issues.redhat.com/browse/JGRP-2478 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. > This requires a few code changes: > * There's no need to pool fibers, see [1] for details > * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThreadExecutor()}} > * In a future version, we could simply remove the 2 thread pool > [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2478) Fibers: test performance versus regular threads

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2478?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2478: --------------------------- Description: Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. This requires a few code changes: * There's no need to pool fibers, see [1] for details * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThradExecutor()}} * In a future version, we could simply remove the 2 thread pool [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] was:Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}} > Fibers: test performance versus regular threads > ----------------------------------------------- > > Key: JGRP-2478 > URL: https://issues.redhat.com/browse/JGRP-2478 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > Test performance on the latest JDK-15-loom with {{use_fibers="true"/"false"}}. > This requires a few code changes: > * There's no need to pool fibers, see [1] for details > * If fibers are used, {{thread_pool}} and {{internal_pool}} in {{TP}} could be assigned the result of {{Executors.newVirtualThradExecutor()}} > * In a future version, we could simply remove the 2 thread pool > [1] [https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part1.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13633) Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi... ] Michael Musgrove commented on WFLY-13633: ----------------------------------------- Okay I see the issue. > Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR > ------------------------------------------------------------------------------------- > > Key: WFLY-13633 > URL: https://issues.redhat.com/browse/WFLY-13633 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... does not remove the JNDI name from the list of names that Narayana will treat as CMR resources as it is removed from a copy of the map: https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060... > This means that if Narayana encounters another resource at a later time with the same JNDI name it will consider it is a CMR resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5475) Externalize lambda for rule attributes

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5475: ----------------------------------------- Summary: Externalize lambda for rule attributes Key: DROOLS-5475 URL: https://issues.redhat.com/browse/DROOLS-5475 Project: Drools Issue Type: Sub-task Components: executable model Affects Versions: 7.39.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi lambdas for dynamic rule attributes are not externalized. e.g. RuleAttributesTest#testDynamicSalience -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5474) Externalize lambda for conditional and named consequences

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5474: ----------------------------------------- Summary: Externalize lambda for conditional and named consequences Key: DROOLS-5474 URL: https://issues.redhat.com/browse/DROOLS-5474 Project: Drools Issue Type: Sub-task Components: executable model Affects Versions: 7.39.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi lambdas for "if" conditional elements are not externalized. e.g. NamedConsequencesTest#testBreakingNamedConsequence -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5473) Implement DefineFunction scheleton

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5473: ---------------------------------------- Summary: Implement DefineFunction scheleton Key: DROOLS-5473 URL: https://issues.redhat.com/browse/DROOLS-5473 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Implement DefineFunction management scheleton. DefineFunctions are similar to DerivedFields, since both make usage of EXPRESSION. Differences are 1) DerivedFields methods should referenced inside "transformations" map, DefineFunctions not 2) DerivedFields methods names are automatically generated, while DefineFunctions ones are retrieved from DefinedFunctions declaration 3) DefineFunctions requires at least one Parameter (beside the List of already defined fields ) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13632) If a CMR resource is deployed concurrently then it will overwrite the list of resources that are expected to behave as CMR

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/WFLY-13632?page=com.atlassian.jira.plugi... ] Michael Musgrove commented on WFLY-13632: ----------------------------------------- My understanding is that the WildFly management model locks out concurrent modifications. We should have someone from the wildfly core team evaluate this bug report. > If a CMR resource is deployed concurrently then it will overwrite the list of resources that are expected to behave as CMR > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13632 > URL: https://issues.redhat.com/browse/WFLY-13632 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > > Inspecting https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... we can see that it will overwrite the map in https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060... because it first get's a copy of a map (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... -> https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060...) so the maps won't be equal. > This will result in WildFly overwriting the list of resources that Narayana will treat as CMR. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2485: -------------------------------- I suggest try your UDP config (as XML) with a sample standalone JGroups app (e.g. Chat), to see if communication works. Verify that UDP.bind_addr,bind_port,mcast_addr are all set correctly > UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2 > -------------------------------------------------------------------- > > Key: JGRP-2485 > URL: https://issues.redhat.com/browse/JGRP-2485 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Reporter: Janardhan Naidu > Assignee: Bela Ban > Priority: Major > Attachments: noapp.log.D20200619.T053202_NODE1 > > > Hi Team, > > we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working. > after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP. > *Warnings:* > *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead* > [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField > *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored* > [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init > *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false* > > To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar: > and now our properties looks like: > *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2) > > > With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP. > Please help me in resolving the same > > Thank > Janardhan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2

by Rashmi Acharya (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Rashmi Acharya commented on JGRP-2485: -------------------------------------- Hi Bela We are not able to upgrade to supported version of Jgroups with this error. We have many customers who are using UDP for their cluster communication and without understanding the root cause and underlying architectute change we are not able to make progress on code side. Your help is really required on why we are not able to make it work with old configurations and how can we debug this issue further. Thanks in advance ! > UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2 > -------------------------------------------------------------------- > > Key: JGRP-2485 > URL: https://issues.redhat.com/browse/JGRP-2485 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Reporter: Janardhan Naidu > Assignee: Bela Ban > Priority: Major > Attachments: noapp.log.D20200619.T053202_NODE1 > > > Hi Team, > > we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working. > after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP. > *Warnings:* > *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead* > [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField > *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored* > [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init > *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false* > > To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar: > and now our properties looks like: > *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2) > > > With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP. > Please help me in resolving the same > > Thank > Janardhan -- This message was sent by Atlassian Jira (v7.13.8#713008)

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