Hello, I'm hoping someone can shed some light on something that I have limited info to provide. This is a shot in the dark... I have several processes that I have created with many different work item implementations that I've created. They all work wonderfully...or they did. Suddenly, I'm having some odd behavior on my servers. 1. Some processes (only some, not all) suddenly will not map result values into the process variables on completion. 2. Any onEntry or onExit actions "crash" (I know that's a vague term) the process. 3. Splits seem to randomly choose the resulting path. I've spent three days on this doing the stare-and-compare to no avail. When I attempt to debug these processes in Eclipse, everything runs perfectly. My first thought is that I was not including the correct jars on my servers. This still may be the case, but I was hoping someone knew something I didn't. Thanks in advance for any help, Paul -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-inconsist... 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

Actually, no. That is more of the odd behavior. Everything seems to continue on it's merry way as if it's doing the right thing. If you were to look at just the logs, it would appear as things ran correctly. The audit logs appear valid as well. To correct my statement slightly, I do get a stack trace when it encounters a onEntry or onExit action in the failing flows: java.lang.NoSuchMethodError: mycompany.edi.Process_mycompany_edi_0.action0(Lorg/drools/spi/KnowledgeHelper;Lorg/drools/spi/ProcessContext;)V at mycompany.edi.Process_mycompany_edi_0Action0Invoker.execute(Process_mycompany_edi_0Action0Invoker.java:20) at org.drools.workflow.instance.impl.ExtendedNodeInstanceImpl.executeAction(ExtendedNodeInstanceImpl.java:66) at org.drools.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerEvent(ExtendedNodeInstanceImpl.java:45) at org.drools.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:36) at org.drools.workflow.instance.node.EventBasedNodeInstance.triggerCompleted(EventBasedNodeInstance.java:96) at org.drools.workflow.instance.node.EventBasedNodeInstance.triggerCompleted(EventBasedNodeInstance.java:77) at org.drools.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:192) at org.drools.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:246) at org.drools.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:222) at org.drools.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:258) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:96) at com.mycompany.drools.process.workitemhandler.ParentWorkItemHandler.executeWorkItem(ParentWorkItemHandler.java:66) at com.mycompany.drools.process.workitemhandler.ChildWorkItemHandler.executeWorkItem(ChildWorkItemHandler.java:37) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:55) at org.drools.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:95) at org.drools.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:111) at org.drools.workflow.instance.impl.NodeInstanceImpl.triggerConnection(NodeInstanceImpl.java:141) at org.drools.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:128) at org.drools.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.drools.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.drools.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:111) at org.drools.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:16) at org.drools.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:185) at org.drools.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:230) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1639) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:272) ... -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-inconsist... 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

I am using Drools 5.0.1 jars on both the server and in Eclipse. It very well may be that some sub-dependency has a different version. The stare-and-compare on 200+ dependencies is driving me to the crazy house. I've even wiped the development server clean, and only copied current dependencies from my included projects in my successful debugging scope. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-inconsist... 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