July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2486) FD Monitor get stuck on TrasferQueueBundler

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2486?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2486: -------------------------------- As I mentioned on the PR, it is not a good idea to fix something downstream (4.0.22 branch). I suggest you also create a PR for the 4.x branch. I've accepted the PR, but this is the last time I've accepted a downstream PR... > FD Monitor get stuck on TrasferQueueBundler > ------------------------------------------- > > Key: JGRP-2486 > URL: https://issues.redhat.com/browse/JGRP-2486 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.22 > Reporter: lukas brandl > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.24 > > Attachments: Main.java, stack-trace.txt > > > Apparently there is an issue in the FD protocol. When a cluster nodes is disconnected and the disconnect isn't handled by FD_SOCK, FD stops sending heartbeats after a while. This only happens when the queue of the TrasferQueueBundler fills up before the node is suspected. > The stack trace shows that the FD$Monitor is blocked by the bundler. This is probably the reason why the heartbeat timeouts are not noticed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2486) FD Monitor get stuck on TrasferQueueBundler

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2486?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2486: --------------------------- Fix Version/s: 4.0.24 (was: 4.0.23) > FD Monitor get stuck on TrasferQueueBundler > ------------------------------------------- > > Key: JGRP-2486 > URL: https://issues.redhat.com/browse/JGRP-2486 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.22 > Reporter: lukas brandl > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.24 > > Attachments: Main.java, stack-trace.txt > > > Apparently there is an issue in the FD protocol. When a cluster nodes is disconnected and the disconnect isn't handled by FD_SOCK, FD stops sending heartbeats after a while. This only happens when the queue of the TrasferQueueBundler fills up before the node is suspected. > The stack trace shows that the FD$Monitor is blocked by the bundler. This is probably the reason why the heartbeat timeouts are not noticed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5472) Implement ExpressionFunctionUtils

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5472: ---------------------------------------- Summary: Implement ExpressionFunctionUtils Key: DROOLS-5472 URL: https://issues.redhat.com/browse/DROOLS-5472 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Move "Expression" specific code to "ExpressionFunctionUtils" class -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5471) [DMN Designer] Include PMML 4.4 model

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5471: ----------------------------------- Summary: [DMN Designer] Include PMML 4.4 model Key: DROOLS-5471 URL: https://issues.redhat.com/browse/DROOLS-5471 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.40.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes Attachments: logistic-43.pmml, logistic-44.pmml, pmml-43_vs_pmml-44.webm, pmml-version-error.log There is an issue when user tries to include PMML-4.4 model into DMN model. Included models tab doesn't render a name of the model and an error appears in the server log. More info about PMML-4.4 can be found at DROOLS-5451. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2486) FD Monitor get stuck on TrasferQueueBundler

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2486?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2486: --------------------------- Fix Version/s: 4.0.23 > FD Monitor get stuck on TrasferQueueBundler > ------------------------------------------- > > Key: JGRP-2486 > URL: https://issues.redhat.com/browse/JGRP-2486 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.22 > Reporter: lukas brandl > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.23 > > Attachments: Main.java, stack-trace.txt > > > Apparently there is an issue in the FD protocol. When a cluster nodes is disconnected and the disconnect isn't handled by FD_SOCK, FD stops sending heartbeats after a while. This only happens when the queue of the TrasferQueueBundler fills up before the node is suspected. > The stack trace shows that the FD$Monitor is blocked by the bundler. This is probably the reason why the heartbeat timeouts are not noticed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5470) Verifier breaks for multi template key BRL actions

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5470: ----------------------------------- Summary: Verifier breaks for multi template key BRL actions Key: DROOLS-5470 URL: https://issues.redhat.com/browse/DROOLS-5470 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.39.0.Final Reporter: Jozef Marko Assignee: Toni Rikkola Attachments: MySpace_whenandwhere.zip, Screenshot from 2020-06-04 15-12-33.png The Verifier feature throws an error when opening a table that contains specific combination of template keys in BRL action column. It seems as issue of one of columns bound to the template key is Date type. -- 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 Janardhan Naidu (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Janardhan Naidu commented on JGRP-2485: --------------------------------------- HI [~belaban] do we have any updates on this issue.? Thanks Janardhan > 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] (DROOLS-5461) Overall Transformations Workflow

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5461?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5461. ------------------------------------ > Overall Transformations Workflow > -------------------------------- > > Key: DROOLS-5461 > URL: https://issues.redhat.com/browse/DROOLS-5461 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Overall workflow functionality. Not necessarily completely working. Should be able to compile. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5469) User can not select cell of Guided Decision Table

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5469: ----------------------------------- Summary: User can not select cell of Guided Decision Table Key: DROOLS-5469 URL: https://issues.redhat.com/browse/DROOLS-5469 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.39.0.Final Reporter: Jozef Marko Assignee: Toni Rikkola User is unable to select guided decision table data cell by a mouse. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5407) User can not select cell of Guided Decision Table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5407?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5407: -------------------------------- Workaround Description: Option 1 - Select header cell by mouse then navigate into data cells by keyboard arrow keys. Option 2 - Double click cell, cancel edit mode, use keyboard for further navigation was:Select header cell by mouse then navigate into data cells by keyboard arrow keys. > User can not select cell of Guided Decision Table > ------------------------------------------------- > > Key: DROOLS-5407 > URL: https://issues.redhat.com/browse/DROOLS-5407 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.39.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, regression > > User is unable to select guided decision table data cell by a mouse. -- 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