August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1679) FEEL list filter returns empty collection when there are errors evaluating filter

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1679?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1679: ------------------------------------------- Fix Version/s: 7.3.0.Final (was: 7.2.0.Final) > FEEL list filter returns empty collection when there are errors evaluating filter > --------------------------------------------------------------------------------- > > Key: DROOLS-1679 > URL: https://issues.jboss.org/browse/DROOLS-1679 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Priority: Minor > Fix For: 7.3.0.Final > > > When having this FEEL list with filter which is incorrect: > {code:java} > ["a", "b", "c"][a] > {code} > the evaluation returns an empty list instead of null. Output of this test is here: > https://gist.github.com/baldimir/18232741fdf1b425ba84d00d83edb939 > I will provide PR with a reproducer today. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1691) Add method to the DMNRuntime to execute multiple decisions at once

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1691?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1691: ------------------------------------------- Fix Version/s: 7.3.0.Final (was: 7.2.0.Final) > Add method to the DMNRuntime to execute multiple decisions at once > ------------------------------------------------------------------ > > Key: DROOLS-1691 > URL: https://issues.jboss.org/browse/DROOLS-1691 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.3.0.Final > > > The DMN runtime currently has methods to execute: > * all decisions in a model > * a single decision (and its dependencies) by name > * a single decision (and its dependencies) by id > For remote invocation, it is important to add two new methods that take a list of decisions (one by name, the other by id) to execute and return the values in a single call. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1692) Migrate tests in drools-persistence-jpa module from Bitronix to Narayana

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1692?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1692: ------------------------------------------- Fix Version/s: 7.3.0.Final (was: 7.2.0.Final) > Migrate tests in drools-persistence-jpa module from Bitronix to Narayana > ------------------------------------------------------------------------ > > Key: DROOLS-1692 > URL: https://issues.jboss.org/browse/DROOLS-1692 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Fix For: 7.3.0.Final > > > Tests in module drools-persistence-jpa must be migrated to Narayana. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1695) When unmarshalling, the reader returns attributePrefix as null on IBM JDK

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1695?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1695: ------------------------------------------- Fix Version/s: 7.3.0.Final (was: 7.2.0.Final) > When unmarshalling, the reader returns attributePrefix as null on IBM JDK > ------------------------------------------------------------------------- > > Key: DROOLS-1695 > URL: https://issues.jboss.org/browse/DROOLS-1695 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.3.0.Final > > > When running test UnmarshalMarshalTest, a lot of tests fail with similar output [1]. It looks like it is related to getting nulls here when reading attribute prefixes [2]. > [1] https://gist.github.com/baldimir/bbb58fb1dfb3df41b74c012d54895ce9 > [2] https://github.com/kiegroup/drools/blob/b007d9d50d5fa9f7eb4c645f298765dab... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1696) Events that are already expired at insert time, doesn't always produce activations

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1696?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-1696: ------------------------------------------- Fix Version/s: 7.3.0.Final (was: 7.2.0.Final) > Events that are already expired at insert time, doesn't always produce activations > ---------------------------------------------------------------------------------- > > Key: DROOLS-1696 > URL: https://issues.jboss.org/browse/DROOLS-1696 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Fix For: 7.3.0.Final > > > When inserting events that have timestamp in the past and don't have expiration defined (@expires), the events don't always produce activations. See a test example [1]. This test fails "randomly". > I will create a PR with a reproducer. > [1] https://gist.github.com/baldimir/fb9808ce1e6d49c83dc24570b3cb6093 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1698) Augment FEEL AST node at compilation with return type using generics

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1698: -------------------------------------- Summary: Augment FEEL AST node at compilation with return type using generics Key: DROOLS-1698 URL: https://issues.jboss.org/browse/DROOLS-1698 Project: Drools Issue Type: Sub-task Components: dmn engine Reporter: Matteo Mortari Priority: Minor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1697) Augment FEEL AST node at compilation with standard return type

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1697: -------------------------------------- Summary: Augment FEEL AST node at compilation with standard return type Key: DROOLS-1697 URL: https://issues.jboss.org/browse/DROOLS-1697 Project: Drools Issue Type: Sub-task Components: dmn engine Reporter: Matteo Mortari Priority: Minor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1697) Augment FEEL AST node at compilation with standard return type

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1697?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-1697: -------------------------------------- Assignee: Matteo Mortari > Augment FEEL AST node at compilation with standard return type > -------------------------------------------------------------- > > Key: DROOLS-1697 > URL: https://issues.jboss.org/browse/DROOLS-1697 > Project: Drools > Issue Type: Sub-task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2209) Members leaving the cluster

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2209?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2209: -------------------------------- Hi Swathi, please don't use JIRA to report problems; this is for real bugs or new features... Having said that, I have a few questions: * Why didn't you upgrade to 3.6.x (the latest?) Why to an *alpha* version? * Is this reproduceable? * You have the weird combination of FD_ALL and FD; this makes no sense! I suggest FD_ALL and FD_SOCK instead * Why did you remove UNICAST3? This will give you dropped / duplicate or unordered point-to-point messages If you want to, we can have an interactive (google hangout with screen sharing) session to get you back on track. Ping me at belaban at mailbox dot org if you're interested. > Members leaving the cluster > --------------------------- > > Key: JGRP-2209 > URL: https://issues.jboss.org/browse/JGRP-2209 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.0 > Environment: Linux > Reporter: Swathi Kumar > Assignee: Bela Ban > > We recently upgraded the jgroups jars from version 2_5_2/jgroups-all.jar to 3_4_0/jgroups-3.4.0.Alpha2.jar. > With the upgrade we see our clusters are not stable. > The members leave the cluster for short duration of time (say around 5-6m) and join back on their own. > We initially suspected it to be a network issue and we involved the network team to investiate further. > But after reviewing the network logs, it is very much evident that the network has no role to play in members leaving the cluster. The boxes on which the nodes/members are running are healthy and fine and the network is very fast and healthy too. > We are not able to determine the root cause for the members leaving the clusters. > Please note, we have multiple clusters configured (round about 5-6) and we are experiencing the same problem on all the clusters. > We request you to kindly help us in resolving this issue. > We have the below jgroups config properties in our application to create 3 channels (for security reasons have used a dummy host name here) :- > jgroups_cluster.property_string=TCP(bind_addr=host_name_A;bind_port=34061):TCPPING(initial_hosts=host_name_A[34061],host_name_A[44061],host_name_A[54061];port_range=1;timeout=5000;num_initial_members=2):MERGE2(min_interval=3000;max_interval=5000):FD_ALL(interval=5000;timeout=20000):FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(retransmit_timeout=100,200,300,600,1200,2400,4800;discard_delivered_msgs=true):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(print_local_addr=true;join_timeout=5000) > jgroups_cluster.distribution_property_string=TCP(bind_port= 34060;thread_pool_rejection_policy=run):TCPPING(initial_hosts=host_name_A[34060],host_name_A[44060],host_name_A[54060];port_range=1;timeout=5000;num_initial_members=2):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(retransmit_timeout=3000;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) > jgroups_cluster.lock.protocolStack=TCP(bind_addr=host_name_A;bind_port=34062:TCPPING(initial_hosts=host_name_A[34062],host_name_A[44062],host_name_A[54062];port_range=1;timeout=5000;num_initial_members=2):MERGE2(min_interval=3000;max_interval=5000):FD_ALL(interval=5000;timeout=20000):FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(retransmit_timeout=100,200,300,600,1200,2400,4800;discard_delivered_msgs=true):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(print_local_addr=true;join_timeout=5000) > Please let us know if you need any logs from our end. > Kindly consider this on priority as our business is at stake with this issue happening on a daily basis. > Many thanks in advance. > Regards > Swathi BN > (IBM) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1694) Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1694?page=com.atlassian.jira.plugi... ] Maciej Swiderski commented on DROOLS-1694: ------------------------------------------ thanks [~mfusco], since you already triaged it then it's all good. > Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin > ---------------------------------------------------------------------------------- > > Key: DROOLS-1694 > URL: https://issues.jboss.org/browse/DROOLS-1694 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.3.0.Final > Reporter: Alistair Black > Assignee: Massimiliano Dessi > > I am working on a multi-module BRMS project, with each module encapsulating a set of rules forming a single knowledge base. There is a "packaging" module which inherits each of these modules in order to generate a KJAR for deployment purposes. The application then utilises this KJAR via the KieScanner/ReleaseId approach to facilitate dynamic rule loading at runtime and decoupling of application/rules. > Having taken the above approach I have encountered an issue where the master build fails when building the "packaging" module as part of the main project build. If the module is built on it's own, then it completes without error. > The error reported is: > {{[ERROR] Failed to execute goal org.kie:kie-maven-plugin:6.3.0.Final:build (default-build) on project rules: Execution default-build of goal org.kie:kie-maven-plugin:6.3.0.Final:build failed: Illegal class for global. Expected [org.drools.template.parser.DefaultGenerator], found [org.drools.template.parser.DefaultGenerator]. -> [Help 1]}} > Having liased with Maciej Swiderski he has asked me to report it as a bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 August 2017