I don't know if that's your problem, but I noticed that calling Session.getObjects() with a JPAknowledgeService halts the rule engine, so when I do session.getObjects(), I have to do a session.fireAllRules() just after -----Message d'origine----- De : rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] De la part de todoanv Envoyé : mercredi 16 juin 2010 12:28 À : rules-users(a)lists.jboss.org Objet : [rules-users] Facts are kept in the working memory instead of triggering rules Hi! I have a problem using Drools with a distributed application. Every node of my application runs its own drools instance and the instances communicate using pipelines. If I put a new fact into Drools it triggers the correct rules locally and propagates the facts to all other nodes in order to trigger the same rules there. In most cases the rules are triggered correctly on the remote nodes. In some cases the facts are put into the working memory but they don't fire the corresponding rules and are kept in the working memory. Can anyone tell me why this problem occurs and what I can do to solve it? Thanks in advance P.S: I'm sorry if this issue was already discussed but I didn't find an existing thread. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Facts-are-kept-in-the... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.