April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1025) NPE removing a rule that contains a subnetwork

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1025?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1025: ------------------------------------------------- Tibor Zimanyi <tzimanyi(a)redhat.com> changed the Status of [bug 1298579|https://bugzilla.redhat.com/show_bug.cgi?id=1298579] from ON_QA to VERIFIED > NPE removing a rule that contains a subnetwork > ---------------------------------------------- > > Key: DROOLS-1025 > URL: https://issues.jboss.org/browse/DROOLS-1025 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Removing a rule containing a subnetwork causes the following NPE: > {code} > java.lang.NullPointerException > at org.drools.core.phreak.AddRemoveRule.deletePeerLeftTuple(AddRemoveRule.java:777) > at org.drools.core.phreak.AddRemoveRule.followPeer(AddRemoveRule.java:749) > at org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:713) > at org.drools.core.phreak.AddRemoveRule.flushStagedTuples(AddRemoveRule.java:281) > at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:153) > at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:173) > at org.drools.core.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:163) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1635) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1626) > at org.drools.core.impl.KnowledgeBaseImpl.internalRemoveRule(KnowledgeBaseImpl.java:1610) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1581) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1089) Reentrant working memory actions aren't flushed immediately even when eager evaluation is forced

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1089?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1089: ------------------------------------------------- Tibor Zimanyi <tzimanyi(a)redhat.com> changed the Status of [bug 1316860|https://bugzilla.redhat.com/show_bug.cgi?id=1316860] from ON_QA to VERIFIED > Reentrant working memory actions aren't flushed immediately even when eager evaluation is forced > ------------------------------------------------------------------------------------------------ > > Key: DROOLS-1089 > URL: https://issues.jboss.org/browse/DROOLS-1089 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.0.CR2, 7.0.0.Final > > > jBPM requires Drools working memory actions to be immediately flushed and then uses Drools force eager activation option. However even when this option is enabled working memory actions that aren't created in a reentrant way (during a rule firing) are enqueued instead of being flushed as expected by jBPM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6449) Upgrade Narayana to 5.3.2.Final

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6449?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated WFLY-6449: ---------------------------------- Fix Version/s: 11.0.0.Alpha1 > Upgrade Narayana to 5.3.2.Final > ------------------------------- > > Key: WFLY-6449 > URL: https://issues.jboss.org/browse/WFLY-6449 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-939) Contents of NegotiationContext getting cleared before challenge is sent to client.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-939?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-939. --------------------------------------- Resolution: Done > Contents of NegotiationContext getting cleared before challenge is sent to client. > ---------------------------------------------------------------------------------- > > Key: SECURITY-939 > URL: https://issues.jboss.org/browse/SECURITY-939 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_3_0_0_Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_2_CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6450) Old JGroups/Netty dependencies in wildfly-jms-client-bom

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6450?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-4035 to WFLY-6450: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6450 (was: JBEAP-4035) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.Final (was: 7.0.0.ER7) > Old JGroups/Netty dependencies in wildfly-jms-client-bom > -------------------------------------------------------- > > Key: WFLY-6450 > URL: https://issues.jboss.org/browse/WFLY-6450 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > > There is different JGroups and Netty version in EAP 7.0.0.ER7 zip and dependencies downloaded by wildfly-jms-client-bom: > {code} > <dependency> > <groupId>org.jboss.eap</groupId> > <artifactId>wildfly-jms-client-bom</artifactId> > <version>7.0.0.ER7-redhat-1</version> > <type>pom</type> > </dependency> > {code} > Actual state: > EAP 7.0.0.ER7 contains Netty 4.0.32 but bom 4.0.30 > EAP 7.0.0.ER7 contains JGroups 3.6.8 but bom 3.6.0 > Expected state: > Those versions should be in sync. > Customer impact: > No issue was found. > Priority can be increased if issue occurs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6449) Upgrade Narayana to 5.3.2.Final

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-6449: ------------------------------------- Summary: Upgrade Narayana to 5.3.2.Final Key: WFLY-6449 URL: https://issues.jboss.org/browse/WFLY-6449 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1110) Avoid acquiring a kbase readlock when performing a working memory action

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1110?page=com.atlassian.jira.plugi... ] Mario Fusco closed DROOLS-1110. ------------------------------- Fix Version/s: 6.4.0.Final 7.0.0.Final Resolution: Done Implemented by https://github.com/droolsjbpm/drools/commit/1e50f13e6 > Avoid acquiring a kbase readlock when performing a working memory action > ------------------------------------------------------------------------- > > Key: DROOLS-1110 > URL: https://issues.jboss.org/browse/DROOLS-1110 > Project: Drools > Issue Type: Enhancement > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.0.Final, 7.0.0.Final > > > At the moment all working memory actions (insert/update/delete) need to acquire a read lock on the kbase. This is avoidable making the kbase to deactivate (through their state machine) all the ksessions created from it before modifying the kbase itself. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1110) Avoid acquiring a kbase readlock when performing a working memory action

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1110: ----------------------------------- Summary: Avoid acquiring a kbase readlock when performing a working memory action Key: DROOLS-1110 URL: https://issues.jboss.org/browse/DROOLS-1110 Project: Drools Issue Type: Enhancement Reporter: Mario Fusco Assignee: Mario Fusco At the moment all working memory actions (insert/update/delete) need to acquire a read lock on the kbase. This is avoidable making the kbase to deactivate (through their state machine) all the ksessions created from it before modifying the kbase itself. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-711) Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-711?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-711: ---------------------------------- Assignee: Edson Tirelli (was: Mark Proctor) > Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test > ---------------------------------------------------------------------------------------- > > Key: DROOLS-711 > URL: https://issues.jboss.org/browse/DROOLS-711 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4, 6.2.0.Final > Environment: kie-server on WildFly 8.2.0.Final running with JDK 8 > Reporter: Matteo Mortari > Assignee: Edson Tirelli > Attachments: 20150213.DROOLS-711.zip > > > I have deployed Kie Server kie-server-distribution-wars-6.2.0.CR4-ee7.war on WildFly 8.2.0.Final. > I have a simple rule base in the project {{client-test-rules}} as per below, in a kie project structured as kie-drools-archetype, which passes all test and install in m2 repo with {{mvn clean install}}. > {code:java} > package com.acme.client_test_rules; > declare Measurement > @role(event) > end > rule "keep latest Measurement ID" > salience 1000 > no-loop > when > $old : Measurement( $id : id ) > $new : Measurement( id == $id , this after $old ) > then > System.out.println("keep latest old : "+$old+" new (kept): "+$new); > retract($old); > end > {code} > Then I issue Kie Server commands, using the client library, using project {{client-test}} to instantiate a container for the same artifact, but in the wildfly logs I get the following error below - which doesn't happen for kie-maven-plugin nor during unit test. Please note I'm assuming user {{kieserver}} with password {{kieserver}} is a valid user for the Kie Server Realm, or configure wildfly or the code in the project {{client-test}} accordingly to your environment =). > {code} > 09:41:41,700 ERROR [org.drools.compiler.kie.builder.impl.AbstractKieModule] (default task-4) Unable to build KieBaseModel:kbase1 > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Field Reader does not exist for declaration '$id' in 'predicate 'id == $id'' in the rule 'keep latest Measurement ID' : [Rule name='keep latest Measurement ID'] > Unable to Analyse Expression id == $id: > [Error: unable to resolve method using strict-mode: com.acme.client_test_rules.Measurement.id()] > [Near : {... id == $id ....}] > ^ > [Line: 12, Column: 4] : [Rule name='keep latest Measurement ID'] > {code} > Can you kindly verify if some bug is hiding behind this odd behavior, please? > Thank you > MM -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-711) Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test

by Kaan Bingol (JIRA)

[ https://issues.jboss.org/browse/DROOLS-711?page=com.atlassian.jira.plugin... ] Kaan Bingol commented on DROOLS-711: ------------------------------------ I think the issue still persists in 6.3.0.Final. I have tested in a similar setup to the reported one. Client driver project only depends on kie-ci 6.3.0.Final and when the kie container is tried to be constructed, kie module unable to build due to the same reasons. However, if I remove "declare" statement from the rule file, it works or if I add the dependency of rules project (the one that build and uploaded into maven repository) into the main container project pom while still constructing the kie container from maven repo the issue is also gone. However, both are not a feasible solutions since declare statement is used for CEP and adding dependency contradicts whole building kie container from maven repository concept. > Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test > ---------------------------------------------------------------------------------------- > > Key: DROOLS-711 > URL: https://issues.jboss.org/browse/DROOLS-711 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4, 6.2.0.Final > Environment: kie-server on WildFly 8.2.0.Final running with JDK 8 > Reporter: Matteo Mortari > Assignee: Mark Proctor > Attachments: 20150213.DROOLS-711.zip > > > I have deployed Kie Server kie-server-distribution-wars-6.2.0.CR4-ee7.war on WildFly 8.2.0.Final. > I have a simple rule base in the project {{client-test-rules}} as per below, in a kie project structured as kie-drools-archetype, which passes all test and install in m2 repo with {{mvn clean install}}. > {code:java} > package com.acme.client_test_rules; > declare Measurement > @role(event) > end > rule "keep latest Measurement ID" > salience 1000 > no-loop > when > $old : Measurement( $id : id ) > $new : Measurement( id == $id , this after $old ) > then > System.out.println("keep latest old : "+$old+" new (kept): "+$new); > retract($old); > end > {code} > Then I issue Kie Server commands, using the client library, using project {{client-test}} to instantiate a container for the same artifact, but in the wildfly logs I get the following error below - which doesn't happen for kie-maven-plugin nor during unit test. Please note I'm assuming user {{kieserver}} with password {{kieserver}} is a valid user for the Kie Server Realm, or configure wildfly or the code in the project {{client-test}} accordingly to your environment =). > {code} > 09:41:41,700 ERROR [org.drools.compiler.kie.builder.impl.AbstractKieModule] (default task-4) Unable to build KieBaseModel:kbase1 > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Field Reader does not exist for declaration '$id' in 'predicate 'id == $id'' in the rule 'keep latest Measurement ID' : [Rule name='keep latest Measurement ID'] > Unable to Analyse Expression id == $id: > [Error: unable to resolve method using strict-mode: com.acme.client_test_rules.Measurement.id()] > [Near : {... id == $id ....}] > ^ > [Line: 12, Column: 4] : [Rule name='keep latest Measurement ID'] > {code} > Can you kindly verify if some bug is hiding behind this odd behavior, please? > Thank you > MM -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

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 April 2016