September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-3120) Error - no visitor implementation for : class org.jbpm.ruleflow.core.RuleFlowProcess

by shashi mhatre (JIRA)

Error - no visitor implementation for : class org.jbpm.ruleflow.core.RuleFlowProcess ------------------------------------------------------------------------------------ Key: JBRULES-3120 URL: https://issues.jboss.org/browse/JBRULES-3120 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: 5.1.0.FINAL Environment: Windows XP, Java 1.6.23 Reporter: shashi mhatre Assignee: Mark Proctor Drools KnowledgeAgent print below message on console after executing rules. "no visitor implementation for : class org.jbpm.ruleflow.core.RuleFlowProcess : org.jbpm.ruleflow.core.RuleFlowProcess@5d5660fe" This happens when "NewInstance" property of the knowledgeAgent is set to false. I have configured one BPMN process and a simple DRL file in the changeset. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3109) drools-flow: deadlock for concurrent process completions in oracle

by Jordi Alvarez (JIRA)

drools-flow: deadlock for concurrent process completions in oracle ------------------------------------------------------------------ Key: JBRULES-3109 URL: https://issues.jboss.org/browse/JBRULES-3109 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow) Affects Versions: 5.1.1.FINAL Environment: Use of Oracle RDBMS as the dabase system Reporter: Jordi Alvarez Assignee: Mark Proctor Hello, we are using drools-flow with JPA, using Hibernate and Oracle RDBMS. We do have multiple concurrent stateful sessions. We also make extensive use of timers. Additionally, we need a blocking system that guarantees that only one request is executing concurrently for a stateful session. We have checked that out bloquing system is working correctly. This blocking system takes into account timers also. In this context, we have detected a situation in which deadlocks are produced when several process instances are tried to be deleted concurrently. The deleted process instances do not need to have anything in common. The database sessions involved in the deadlock report always to be performed when they are executing: DELETE FROM ProcessInstanceInfo WHERE InstanceId = :1 AND OPTLOCK = :2 Which corresponds to the removal of a process. Looking into database locks acquired by sessions it can be seen that the table over whichthe deadlock is produced is EVENTTYPES. The problem is indeed caused when the cascade on delete is applied. Whenever a ProcessInstanceInfo row is deleted, this produces to delete all EVENTTYPES records associated with that process instance. Oracle locks the EVENTTYPES table with mode S/Row-X (SSX) . Additionally, it locks the deleted rows with mode Row-X (SX). Whenever several ProcessInstanceInfo rows are deleted concurrently, there are several database sessions performing these locks concurrently, which is the cause of the deadlock. A more generic description of the situation can be found in: http://www.mail-archive.com/hibernate-devel@lists.sourceforge.net/msg0549... As it is suggested in this link, the creation of an index over EVENTTYPES foreign key for ProcessInstanceInfo solves the problem. The index we have created is a simple one over the foreign key, as follows: CREATE INDEX IDX_EVENTTYPES ON EVENTTYPES (INSTANCEID); It would be nice that the automatically created tables contains that index. Alternatively, the documentation should contain some addendum regarding the database tables created, in order to create the index manually, at least for the Oracle database. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3190) NPE when updating fact

by Tomáš Schlosser (JIRA)

NPE when updating fact ---------------------- Key: JBRULES-3190 URL: https://issues.jboss.org/browse/JBRULES-3190 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.3.0.Beta1 Reporter: Tomáš Schlosser Assignee: Mark Proctor Take the example project from JBRULES-2887 and run it. You'll get this exception: Exceuting ruleorg.drools.runtime.rule.ConsequenceException: rule: MESSAGE_HELLO at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1093) at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1022) at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1243) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:733) at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:699) at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:218) at com.sample.DroolsTest.main(DroolsTest.java:41) Caused by: java.lang.NullPointerException at org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:576) at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:265) at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:465) at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:365) at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:294) at com.sample.Rule_MESSAGE_HELLO_0.defaultConsequence(Rule_MESSAGE_HELLO_0.java:8) at com.sample.Rule_MESSAGE_HELLO_0DefaultConsequenceInvoker.evaluate(Rule_MESSAGE_HELLO_0DefaultConsequenceInvoker.java:27) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1083) ... 6 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3069) Upgrading definition of a persistent process instance causes it to pick up the updated process definition

by Anton Litvinenko (JIRA)

Upgrading definition of a persistent process instance causes it to pick up the updated process definition --------------------------------------------------------------------------------------------------------- Key: JBRULES-3069 URL: https://issues.jboss.org/browse/JBRULES-3069 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Reporter: Anton Litvinenko Assignee: Mark Proctor I have a process with 3 nodes: Action Node (writing to system.out) => Async Work Item (makes request and then waits for async result - not blocking) => Action Node (writing to system.out) So, I experimented like this: 1. started the process, saw first system.out, saw making request 2. updated the process to have a different system.out at last action node, deployed it to Guvnor, waited for KnowledgeAgent to pick it up 3. sent response to the process at Async Work Item -> saw *new* system.out at the last node. Some discussion is available here: http://drools.46999.n3.nabble.com/Drools-Flow-5-1-Updating-a-process-defi... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3180) FIX queryCommand for variable serialization

by Mauricio Salatino (JIRA)

FIX queryCommand for variable serialization ------------------------------------------- Key: JBRULES-3180 URL: https://issues.jboss.org/browse/JBRULES-3180 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mauricio Salatino we need to be sure that serialization of the arguments is done right: for (int j = 0; j < arguments.size(); j++) { if (arguments.get(j) instanceof Variable) { arguments.set(j, Variable.v); } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3167) Null pointer exception with multithread enabled

by Pascal de Kloe (JIRA)

Null pointer exception with multithread enabled ----------------------------------------------- Key: JBRULES-3167 URL: https://issues.jboss.org/browse/JBRULES-3167 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.Final Reporter: Pascal de Kloe Assignee: Mark Proctor ******************************************************************************************************* Partition task manager caught an unexpected exception: null Drools is capturing the exception to avoid thread death. Please report stack trace to development team. java.lang.NullPointerException at org.drools.core.util.LeftTupleIndexHashTable.remove(LeftTupleIndexHashTable.java:285) at org.drools.reteoo.NotNode.assertObject(NotNode.java:144) at org.drools.reteoo.PartitionTaskManager$FactAssertAction.execute(PartitionTaskManager.java:272) at org.drools.reteoo.PartitionTaskManager$PartitionTask.run(PartitionTaskManager.java:116) at org.drools.concurrent.ExternalExecutorService$ObservableRunnable.run(ExternalExecutorService.java:443) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3194) Generate invoker classes with ASM

by Mario Fusco (JIRA)

Generate invoker classes with ASM --------------------------------- Key: JBRULES-3194 URL: https://issues.jboss.org/browse/JBRULES-3194 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Generate invoker classes with ASM -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3203) JMSTaskClientConnector doesn't dequeue received messages

by Frank23 Knoll23 (JIRA)

JMSTaskClientConnector doesn't dequeue received messages -------------------------------------------------------- Key: JBRULES-3203 URL: https://issues.jboss.org/browse/JBRULES-3203 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: apache-activemq-5.5.0 as a JMS provider Reporter: Frank23 Knoll23 Assignee: Mark Proctor Hi, org.jbpm.task.service.jms.JMSTaskClientConnector doesn't dequeue received messages from it's responseQueue. Cheers, Frank -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3222) Error unmarshalling knowledgeSession with Facts inserted in entry-points

by Stefan Wehner (JIRA)

Error unmarshalling knowledgeSession with Facts inserted in entry-points ------------------------------------------------------------------------ Key: JBRULES-3222 URL: https://issues.jboss.org/browse/JBRULES-3222 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1, 5.2.0.Final Reporter: Stefan Wehner Assignee: Mark Proctor When trying to marshall and then unmarshall a StatefulKnowledgeSession where a Fact has been inserted into an entry-point a NullPointerException is thrown: java.lang.NullPointerException at org.drools.reteoo.RuleTerminalNodeLeftTuple.<init>(RuleTerminalNodeLeftTuple.java:151) at org.drools.reteoo.RuleTerminalNode.createLeftTuple(RuleTerminalNode.java:608) at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarshaller.java:523) at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMarshaller.java:373) at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshaller.java:230) at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarshaller.java:92) at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarshaller.java:63) at com.sample.DroolsTest.main(DroolsTest.java:50) Provided is a testcase with two simple rules matching Fact objects directly and from the entry-point "facts". A fact is inserted directly into the knowledgeSession and then it is marshalled and unmarshalled - which works fine. Then a fact is inserted into a entry-point "facts" and the session is marshalled and unmarshalled - which throws the NPE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (SECURITY-617) PicketBoxSecurityVault should consider system property for Keystore URL

by Anil Saldhana (JIRA)

PicketBoxSecurityVault should consider system property for Keystore URL ----------------------------------------------------------------------- Key: SECURITY-617 URL: https://issues.jboss.org/browse/SECURITY-617 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_v4_0_2 Reporter: Anil Saldhana Assignee: Anil Saldhana Currently only the enc dir can take in system prop. we need to that for the keystore url too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
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 September 2011