August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5095) [DMN Designer] Investigate performance switching between editor instances

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5095?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5095: ------------------------------------------- Fix Version/s: 7.42.0.Final (was: 7.41.0.Final) > [DMN Designer] Investigate performance switching between editor instances > ------------------------------------------------------------------------- > > Key: DROOLS-5095 > URL: https://issues.redhat.com/browse/DROOLS-5095 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Fix For: 7.42.0.Final > > Attachments: switch-dmn.webm > > > This JIRA is to investigate the reported performance issue switching between different DMN Designer instances in Business Central. > The issue was noticed by [~jomarko] when testing DROOLS-5058 (although the fix therein should have had *zero* affect on switching). > For more details see the video [^switch-dmn.webm] > h2. Manual acceptance test > - Prepare 5 DMN models in project > - Open all in parallel > - Try to switch between them, keep all opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-2254?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-2254: ------------------------------------------- Fix Version/s: 7.42.0.Final (was: 7.41.0.Final) > Automate .proto files rebuild in pom.xml > ---------------------------------------- > > Key: DROOLS-2254 > URL: https://issues.redhat.com/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.42.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-3160?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.42.0.Final (was: 7.41.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.redhat.com/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.42.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4830) Add a Docker composer to connect BC and Kie Server images

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4830?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-4830: ------------------------------------------- Fix Version/s: 7.42.0.Final (was: 7.41.0.Final) > Add a Docker composer to connect BC and Kie Server images > --------------------------------------------------------- > > Key: DROOLS-4830 > URL: https://issues.redhat.com/browse/DROOLS-4830 > Project: Drools > Issue Type: Feature Request > Components: docker images > Affects Versions: 7.30.0.Final > Reporter: Ricardo Zanini Fernandes > Assignee: Ricardo Zanini Fernandes > Priority: Major > Fix For: 7.42.0.Final > > > It's natural to have BC and KIE servers working together. Would be nice to have a Docker composer file that fires up the two instances at once. This will support use cases such authoring on BC and deploying in the connected KIE Server. > References: https://www.drools.org/download/download.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1522) NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-1522?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-1522: --------------------------- Description: If become_server_queue_size in NAKACK2 is > 0, both protocols buffer messages sent before is_server=true, and replay them when the first view is received or when a BECOME_SERVER event is received. There are 2 issues associated with this: #1 When flushing the become_server_queue, we should never call up(Event) directly (use the thread pool). [This is not the issue that's causing this though] #2 When the queue is flushed on the first view change, this might trigger messages to be delivered to the application, which in turn might send messages (all on the same thread, because of #1). As the channel is yet unconnected, the message send will trigger an exception, which causes the JOIN to fail ! SOLUTION: - Flush become_server_queue in a separate task (good practice to do this on a separate thread anyway !) - Only flush the become_server_queue when receiving a BECOME_SERVER event, *not* when receiving the first view change was: If become_server_queue_size in NAKACK{2} is > 0, both protocols buffer messages sent before is_server=true, and replay them when the first view is received or when a BECOME_SERVER event is received. There are 2 issues associated with this: #1 When flushing the become_server_queue, we should never call up(Event) directly (use the thread pool). [This is not the issue that's causing this though] #2 When the queue is flushed on the first view change, this might trigger messages to be delivered to the application, which in turn might send messages (all on the same thread, because of #1). As the channel is yet unconnected, the message send will trigger an exception, which causes the JOIN to fail ! SOLUTION: - Flush become_server_queue in a separate task (good practice to do this on a separate thread anyway !) - Only flush the become_server_queue when receiving a BECOME_SERVER event, *not* when receiving the first view change > NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel > -------------------------------------------------------------------------------------------------- > > Key: JGRP-1522 > URL: https://issues.redhat.com/browse/JGRP-1522 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 3.2 > > Attachments: tmp.log > > > If become_server_queue_size in NAKACK2 is > 0, both protocols buffer messages sent before is_server=true, and replay them when the first view is received or when a BECOME_SERVER event is received. > There are 2 issues associated with this: > #1 When flushing the become_server_queue, we should never call up(Event) directly (use the thread pool). [This is not the issue that's causing this though] > #2 When the queue is flushed on the first view change, this might trigger messages to be delivered to the application, which in turn might send messages (all on the same thread, because of #1). As the channel is yet unconnected, the message send will trigger an exception, which causes the JOIN to fail ! > SOLUTION: > - Flush become_server_queue in a separate task (good practice to do this on a separate thread anyway !) > - Only flush the become_server_queue when receiving a BECOME_SERVER event, *not* when receiving the first view change -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1522) NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-1522?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-1522: --------------------------- Workaround Description: Set {{NAKACK2.become_server_queue_size}} to 0 (was: Set NAKACK{2}.become_server_queue_size to 0) > NAKACK / NAKACK2: flushBecomeServerQueue() might trigger sending of message on unconnected channel > -------------------------------------------------------------------------------------------------- > > Key: JGRP-1522 > URL: https://issues.redhat.com/browse/JGRP-1522 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 3.2 > > Attachments: tmp.log > > > If become_server_queue_size in NAKACK{2} is > 0, both protocols buffer messages sent before is_server=true, and replay them when the first view is received or when a BECOME_SERVER event is received. > There are 2 issues associated with this: > #1 When flushing the become_server_queue, we should never call up(Event) directly (use the thread pool). [This is not the issue that's causing this though] > #2 When the queue is flushed on the first view change, this might trigger messages to be delivered to the application, which in turn might send messages (all on the same thread, because of #1). As the channel is yet unconnected, the message send will trigger an exception, which causes the JOIN to fail ! > SOLUTION: > - Flush become_server_queue in a separate task (good practice to do this on a separate thread anyway !) > - Only flush the become_server_queue when receiving a BECOME_SERVER event, *not* when receiving the first view change -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4873) Upgrade JGit to 5.8.0.202006091008-r

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4873?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4873: -------------------------------- Description: In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way. Additional dependencies to org.bouncycastle 1.65 are also required was:In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way. > Upgrade JGit to 5.8.0.202006091008-r > ------------------------------------ > > Key: WFCORE-4873 > URL: https://issues.redhat.com/browse/WFCORE-4873 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Management > Affects Versions: 11.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 13.0.0.Beta2 > > > In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way. > Additional dependencies to org.bouncycastle 1.65 are also required -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5532) Drools-core additional cleanups

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5532?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5532: -------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Drools-core additional cleanups > ------------------------------- > > Key: DROOLS-5532 > URL: https://issues.redhat.com/browse/DROOLS-5532 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Daniele Zonca > Assignee: Mario Fusco > Priority: Major > > * Split implementation of KnowledgeBuilderFactoryServiceImpl to remove newJaxbConfiguration so that we can remove KogitoKnowledgeBuilderFactoryServiceImpl duplication > * KieModuleModelImpl move nested classes somewhere else to make it possible reuse the class alone > * Implement something similar to [KogitoTimerServiceFactory|https://github.com/kiegroup/kogito-runtimes/blo...] directly in kie7 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5556) Make mvel to run with java 14 and deploy a new release

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5556: ----------------------------------- Summary: Make mvel to run with java 14 and deploy a new release Key: DROOLS-5556 URL: https://issues.redhat.com/browse/DROOLS-5556 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5538) DMN strongly typed class compile errors for collection types

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5538?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5538: -------------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > DMN strongly typed class compile errors for collection types > ------------------------------------------------------------ > > Key: DROOLS-5538 > URL: https://issues.redhat.com/browse/DROOLS-5538 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > If we have an itemDefinition with isCollection="true", it will cause a compile error for InputSet and OutputSet when typesafe is enabled. Note that itemComponent with isCollection="true" works fine. > DMNRuntimeTypesTest.testCollectionType() > {code:xml} > <semantic:itemDefinition label="tPersonList" name="tPersonList" isCollection="true"> > <semantic:typeRef>tPerson</semantic:typeRef> > </semantic:itemDefinition> > {code} > Consider separating TypeSafe specific tests: > https://github.com/kiegroup/drools/pull/2993#discussion_r463500865 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020