January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2083) [Guided Decision Table] DSL can not contain $ in the definition

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2083?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2083: ----------------------------------- Sprint: 2018 Week 03-04 > [Guided Decision Table] DSL can not contain $ in the definition > --------------------------------------------------------------- > > Key: DROOLS-2083 > URL: https://issues.jboss.org/browse/DROOLS-2083 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Fix For: 7.6.0.Final > > > The DSL sentences are defined like: > - [when] *definition* = real rule > If the *definition* contains *$* character, then the DSL sentence can not be used properly in the guided decision table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-2207: -------------------------------------- [~tirelli] Not an issue in master, but checking 7.5.x now while looking at RHDM-224. > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final, 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3375) Upgrade jboss-logmanager from 2.1.0.Alpha5 to 2.1.0.Alpha6

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3375?page=com.atlassian.jira.plugi... ] Romain Pelisse updated WFCORE-3375: ----------------------------------- Affects Version/s: 3.0.9.Final (was: 3.0.10.Final) > Upgrade jboss-logmanager from 2.1.0.Alpha5 to 2.1.0.Alpha6 > ---------------------------------------------------------- > > Key: WFCORE-3375 > URL: https://issues.jboss.org/browse/WFCORE-3375 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 3.0.9.Final > Reporter: James Perkins > Assignee: James Perkins > Labels: downstream_dependency > > The {{org.jboss.logmanager:jboss-logmanager:2.1.0.Alpha6}} will introduce a new {{CallerClassLoaderLogContextListener}} which needs to be used to ensure that modules don't create loggers on a deployments log context. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3375) Upgrade jboss-logmanager from 2.1.0.Alpha5 to 2.1.0.Alpha6

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3375?page=com.atlassian.jira.plugi... ] Romain Pelisse updated WFCORE-3375: ----------------------------------- Affects Version/s: 3.0.10.Final > Upgrade jboss-logmanager from 2.1.0.Alpha5 to 2.1.0.Alpha6 > ---------------------------------------------------------- > > Key: WFCORE-3375 > URL: https://issues.jboss.org/browse/WFCORE-3375 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 3.0.9.Final > Reporter: James Perkins > Assignee: James Perkins > Labels: downstream_dependency > > The {{org.jboss.logmanager:jboss-logmanager:2.1.0.Alpha6}} will introduce a new {{CallerClassLoaderLogContextListener}} which needs to be used to ensure that modules don't create loggers on a deployments log context. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2210) Drools 7.3.0 serialization null pointer exceptions with sliding windows

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2210?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2210: --------------------------------------- [~connect.manjunath] did you check if the error still occurs with 7.5.0? > Drools 7.3.0 serialization null pointer exceptions with sliding windows > ----------------------------------------------------------------------- > > Key: DROOLS-2210 > URL: https://issues.jboss.org/browse/DROOLS-2210 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.3.0.Final > Reporter: Manjunath S Paramesan > Assignee: Mario Fusco > Priority: Critical > > We have a fairly large rule-base with temporal reasoning and sliding windows. > While serializing the drools session we observe random null pointer exceptions as see below: > Exception in thread "pool-92-thread-98" java.lang.NullPointerException > at org.drools.core.rule.SlidingTimeWindow$BehaviorJobContextTimerOutputMarshaller.serialize(SlidingTimeWindow.java:323) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeTimers(ProtobufOutputMarshaller.java:880) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.serializeSession(ProtobufOutputMarshaller.java:210) > at org.drools.core.marshalling.impl.ProtobufOutputMarshaller.writeSession(ProtobufOutputMarshaller.java:118) > at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:162) > at org.drools.core.marshalling.impl.ProtobufMarshaller.marshall(ProtobufMarshaller.java:146) > at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.backupKieSession(DroolsClientImpl.java:743) > at com.mlnms.common.fmwk.drools.impl.DroolsClientImpl.lambda$processStatefulEvents$0(DroolsClientImpl.java:506) > at java.lang.Thread.run(Thread.java:745) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2171) NullPointerException in drools core

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2171?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2171: --------------------------------------- Can you please provide more information and a reproducer? > NullPointerException in drools core > ------------------------------------ > > Key: DROOLS-2171 > URL: https://issues.jboss.org/browse/DROOLS-2171 > Project: Drools > Issue Type: Bug > Reporter: Yun Lin > Assignee: Mario Fusco > Priority: Critical > Labels: downstream_dependency > > After running for a couple hours, it got the follow NPE. > java.lang.NullPointerException: null > at org.drools.core.common.TupleSetsImpl.setNextTuple(TupleSetsImpl.java:349) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.common.TupleSetsImpl.removeUpdate(TupleSetsImpl.java:205) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.common.TupleSetsImpl.addDelete(TupleSetsImpl.java:110) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.SegmentPropagator.processPeerDeletes(SegmentPropagator.java:109) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.SegmentPropagator.processPeers(SegmentPropagator.java:48) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.SegmentPropagator.propagate(SegmentPropagator.java:41) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:347) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1320) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1311) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1299) ~[drools-core-7.4.1.Final.jar:7.4.1.Final] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2083) [Guided Decision Table] DSL can not contain $ in the definition

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2083?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2083: --------------------------------------- I am confused: is the problem in the core engine or in the decision table UI? DSL uses regexp to match sentence fragments, so I believe the $ needs to be escaped to work... something like \$. > [Guided Decision Table] DSL can not contain $ in the definition > --------------------------------------------------------------- > > Key: DROOLS-2083 > URL: https://issues.jboss.org/browse/DROOLS-2083 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Fix For: 7.6.0.Final > > > The DSL sentences are defined like: > - [when] *definition* = real rule > If the *definition* contains *$* character, then the DSL sentence can not be used properly in the guided decision table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3511) Improve test coverage of CLI feature - looping over commands/operations

by Erich Duda (JIRA)

Erich Duda created WFCORE-3511: ---------------------------------- Summary: Improve test coverage of CLI feature - looping over commands/operations Key: WFCORE-3511 URL: https://issues.jboss.org/browse/WFCORE-3511 Project: WildFly Core Issue Type: Task Components: CLI Affects Versions: 4.0.0.Alpha5 Reporter: Erich Duda Assignee: Erich Duda -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9679) Duplication of TestXAResource under wildfly testsuite

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created WFLY-9679: ------------------------------------- Summary: Duplication of TestXAResource under wildfly testsuite Key: WFLY-9679 URL: https://issues.jboss.org/browse/WFLY-9679 Project: WildFly Issue Type: Enhancement Components: Test Suite Affects Versions: 11.0.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Trivial The testsuite, tests checking XA transactions, contains duplicate code of test {{XAResource}} * https://github.com/wildfly/wildfly/blob/master/testsuite/shared/src/main/... * https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... are almost the same. It would be good to refactor them to reduce code duplication. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Description: The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2. > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018