Mario Fusco created JBRULES-3376: ------------------------------------ Summary: ActivationCancelledEvent causes process to stay in current node Key: JBRULES-3376 URL: https://issues.jboss.org/browse/JBRULES-3376 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Description of problem: If the activation is cancelled by AgendaFilter (getCause() == FILTER) the Ruleflow stops at current Rule Task node and the process never ends. Version-Release number of selected component (if applicable): BRMS-5.3.0.dev5 How reproducible: Every time Steps to Reproduce: 1. Insert events to create Activations 2. Start process with rule task and add event listeners (Process, Agenda) 3. call fireAllRules with AgendaFilter parameter Actual results: Process is never finished nor it moves to next node once no activations are left to fire. Expected results: Process continues once all rules are fired and eventually completes. Additional info: Included workaround shows this problem on StatefulKnowledgeSession although the same problem is on stateless. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira