Hi Dan, did you manage to get it working?<br>I didn't have time to look at your problem yet. I'm having very complicated times, but I'm looking forward to have at least one day to fix that issue.<br>Can you update me your situation right now?<br>
<br><div class="gmail_quote">On Wed, Apr 20, 2011 at 1:26 PM, Dan Nathanson <span dir="ltr"><<a href="mailto:dan@ddnconsulting.com">dan@ddnconsulting.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Bump<br>
<br>
Regards,<br>
<font color="#888888"><br>
Dan Nathanson<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
On Mon, Apr 11, 2011 at 4:37 PM, Dan Nathanson <<a href="mailto:dan@ddnconsulting.com">dan@ddnconsulting.com</a>> wrote:<br>
> Hi Mauricio,<br>
><br>
> This is now happening intermittently for another user and a couple of<br>
> times on our build machine. I have never seen it happen on my<br>
> machine. This will be a show-stopper for us if we cannot figure out<br>
> the cause. Our business processes will stall after one user completes<br>
> their task and the next user is never notified that they have a task,<br>
> and no errors will be reported.<br>
><br>
> Regards,<br>
><br>
> Dan Nathanson<br>
><br>
><br>
><br>
><br>
> On Mon, Apr 4, 2011 at 9:27 PM, Dan Nathanson <<a href="mailto:dan@ddnconsulting.com">dan@ddnconsulting.com</a>> wrote:<br>
>> Hi Mauricio,<br>
>><br>
>> Were you able to make determine anything from the info I sent you?<br>
>><br>
>> Regards,<br>
>><br>
>> Dan Nathanson<br>
>><br>
>> On Fri, Apr 1, 2011 at 11:03 AM, Dan Nathanson <<a href="mailto:dan@ddnconsulting.com">dan@ddnconsulting.com</a>> wrote:<br>
>>> Hi Mauricio,<br>
>>><br>
>>> Thanks for looking into this. These are the types of errors that scare<br>
>>> me. They only happen in one environment and I cannot reproduce them.<br>
>>> How will I know if it happens in production?<br>
>>><br>
>>> We generate our rule flow's dynamically from our own concept of a<br>
>>> process flow. I don't have a custom work item implementation, but I<br>
>>> do have a custom WorkItemHandler registered against work items of type<br>
>>> "Step" called StepWorkItemHandler. StepWorkItemHandler has uses and<br>
>>> injected CallbackHandler to do actual processing. In test code, the<br>
>>> injected callback handler just records what steps (work items) have<br>
>>> been activated. In production code, the injected handler sends JMS<br>
>>> messages to notify assigned users that work needs to be completed.<br>
>>><br>
>>> Below is an example of a simple generated flow that fails<br>
>>> intermittently for one developer here. I captured it using the<br>
>>> XmlRuleFlowProcessDumper.<br>
>>><br>
>>> <?xml version="1.0" encoding="UTF-8"?><br>
>>> <process xmlns="<a href="http://drools.org/drools-5.0/process" target="_blank">http://drools.org/drools-5.0/process</a>"<br>
>>> xmlns:xs="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>"<br>
>>> xs:schemaLocation="<a href="http://drools.org/drools-5.0/process" target="_blank">http://drools.org/drools-5.0/process</a><br>
>>> drools-processes-5.0.xsd"<br>
>>> type="RuleFlow" name="flow-1"<br>
>>> id="bd5556f7_581d_422f_a382_3bb3ac041c4f"<br>
>>> package-name="com.xxx.process.manager" ><br>
>>><br>
>>> <header><br>
>>> <imports><br>
>>> <import name="org.drools.ruleflow.instance.RuleFlowProcessInstance" /><br>
>>> </imports><br>
>>> </header><br>
>>><br>
>>> <nodes><br>
>>> <start id="1" name="flow-1 Start" /><br>
>>> <join id="2" name="step-1 Reject Join" type="2" /><br>
>>> <workItem id="3" name="step-1 Step" ><br>
>>> <work name="Step" ><br>
>>> </work><br>
>>> </workItem><br>
>>> <workItem id="4" name="step-1 Approval" ><br>
>>> <work name="Step" ><br>
>>> </work><br>
>>> </workItem><br>
>>> <split id="5" name="step-1 Approval Split" type="2" ><br>
>>> <constraints><br>
>>> <constraint toNodeId="2" toType="DROOLS_DEFAULT"<br>
>>> name="rejected" priority="110" type="code" dialect="java" >return<br>
>>> true;</constraint><br>
>>> <constraint toNodeId="6" toType="DROOLS_DEFAULT"<br>
>>> name="approved" priority="100" type="rule" dialect="mvel"<br>
>>>>StepApproval( approved == true, sliceValue == "NO_SLICE",<br>
>>> approvalStepNodeId == "1a8a5a64-1e32-46a9-8b04-806c1706a97a"<br>
>>> )</constraint><br>
>>> </constraints><br>
>>> </split><br>
>>> <state id="6" name="null Wait" ><br>
>>> <onEntry><br>
>>> <action type="expression" dialect="java"<br>
>>>>Terminator.terminateFlow(context);</action><br>
>>> </onEntry><br>
>>> <constraints><br>
>>> <constraint toNodeId="7" >Terminator()</constraint><br>
>>> </constraints><br>
>>> </state><br>
>>> <end id="7" name="null End" /><br>
>>> </nodes><br>
>>><br>
>>> <connections><br>
>>> <connection from="1" to="2" /><br>
>>> <connection from="5" to="2" /><br>
>>> <connection from="2" to="3" /><br>
>>> <connection from="3" to="4" /><br>
>>> <connection from="4" to="5" /><br>
>>> <connection from="5" to="6" /><br>
>>> <connection from="6" to="7" /><br>
>>> </connections><br>
>>><br>
>>> </process><br>
>>><br>
>>><br>
>>><br>
>>> I'm attaching the log at trace level (there are no WARN level messages<br>
>>> at all) that shows this flow failing to complete. Lines of interest:<br>
>>> 631: Generating the flow from our internal model<br>
>>> 634: starting the flow<br>
>>> 785: Process event listener shows that flow has started and proceeded<br>
>>> to work item 1 ("step-1 Step")<br>
>>> 802: StepWorkItemHandler called for work item 1 "step-1 Step"<br>
>>> 803: Process event listener shows "unwinding"of activations<br>
>>> 904: Work item 1 "step-1 Step" completed<br>
>>> 921: work item loaded<br>
>>> 939: process instance loaded<br>
>>> 956: Process event listener shows leaving "step-1 Step", activating<br>
>>> work item 2 "step-1 Approval"<br>
>>> 969: StepWorkItemHandler called forwork item 2 "step-1 Approval"<br>
>>> 970: Process event listener shows "unwinding"of activations<br>
>>> 1024: work item 1 deleted<br>
>>> 1032: Work item 2 "step-1 Approval" completed<br>
>>> 1049: work item loaded<br>
>>> 1067: process instance loaded<br>
>>> ---Should now see leaving "step-1 Approval" and completing flow, but<br>
>>> don't see any further progress in the flow.---<br>
>>> 1141: work item 2 deleted<br>
>>><br>
>>> The execution thread is part of the log output and it seems that<br>
>>> everything is done in one thread.<br>
>>><br>
>>> I've also attached a log file (without verbose hibernate output) for a<br>
>>> successful test run.<br>
>>><br>
>>> Regards,<br>
>>><br>
>>> Dan Nathanson<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> On Fri, Apr 1, 2011 at 2:42 AM, Mauricio Salatino <<a href="mailto:salaboy@gmail.com">salaboy@gmail.com</a>> wrote:<br>
>>>> Hi Dan,<br>
>>>> That's strange, it could be related to a non updated version of the fluent<br>
>>>> API.<br>
>>>> Send us the logs with warn verbosity and we will definitely take a look on<br>
>>>> it.<br>
>>>> If the workflow don't continue after a work item completion could be related<br>
>>>> with some kind of threading problem.<br>
>>>> What kind of work item are you implementing? Can you share some test with us<br>
>>>> that shows the desired behavior?<br>
>>>> Greetings.<br>
>>>><br>
>>>> On Thu, Mar 31, 2011 at 4:32 PM, Dan Nathanson <<a href="mailto:dan@ddnconsulting.com">dan@ddnconsulting.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Hi,<br>
>>>>><br>
>>>>> I'm seeing some odd behavior in some of my test cases. And it only<br>
>>>>> seems to happen to one guy. And he's done fresh checkouts of the code,<br>
>>>>> blown away his local M2 repository and verified installed software<br>
>>>>> like OS and Java is same as everyone else's.<br>
>>>>><br>
>>>>> I have some test cases that build up some simple flows programatically<br>
>>>>> using fluent API. Very simple (start --> work item --> work item --><br>
>>>>> state --> end). I am using Drools Flow 5.1.1 with JPA (in-memory H2<br>
>>>>> DB for unit tests). Intermittently, after completing a work item, the<br>
>>>>> flow doesn't continue. Logging in a process event listener shows that<br>
>>>>> the the work item node is never left, although I can see in the logs<br>
>>>>> that the work item is deleted from DB.<br>
>>>>><br>
>>>>> There are no errors, warning or info level messages coming out of<br>
>>>>> Drools or Hibernate prior to the failure.<br>
>>>>><br>
>>>>> It only happens to one guy, but he can reproduce the problem<br>
>>>>> regularly, although it moves around in different test cases and<br>
>>>>> different points in the flows.<br>
>>>>><br>
>>>>> Anyone ever seen this behavior before? Any possible explanations?<br>
>>>>><br>
>>>>> I'd attach the log file, but it is huge since I've got hibernate<br>
>>>>> logging set very verbose.<br>
>>>>><br>
>>>>> Regards,<br>
>>>>><br>
>>>>> Dan Nathanson<br>
>>>>> _______________________________________________<br>
>>>>> rules-users mailing list<br>
>>>>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>>>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> - CTO @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com</a><br>
>>>> - MyJourney @ <a href="http://salaboy.wordpress.com" target="_blank">http://salaboy.wordpress.com</a><br>
>>>> - Co-Founder @ <a href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br>
>>>><br>
>>>> - Salatino "Salaboy" Mauricio -<br>
>>>><br>
>>><br>
>><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br> - CTO @ <a href="http://www.plugtree.com">http://www.plugtree.com</a> <br> - MyJourney @ <a href="http://salaboy.wordpress.com">http://salaboy.wordpress.com</a><br>
- Co-Founder @ <a href="http://www.jbug.com.ar">http://www.jbug.com.ar</a><br> <br> - Salatino "Salaboy" Mauricio -<br>