Thank you very much.

Regards
Tomaso

On Fri, May 23, 2008 at 2:29 PM, John Mettraux <[EMAIL PROTECTED]>
wrote:

>
> On Fri, May 23, 2008 at 7:06 PM, Tomaso Tosolini
> <[EMAIL PROTECTED]> wrote:
> >
> > OpenWFE::ExpressionPool 'expressionPool' - expressionPool operation
> > :do_apply on (fei 0.9.17 engine
> > public/process_definitions/simple_sequence_2.xml
> concurrent_iterator_problem
> > 1 20080523-gutzupuguri.1 cancel-process 0.0.0.0.1) failed with
> > exception : no process to cancel '20080523-gutzupuguri.1'
> >
> /var/www/processmasterdevel/openwferu-densha-0.9.17/vendor/openwfe/expool/expressionpool.rb:419:in
> > `cancel_process'
> >
> /var/www/processmasterdevel/openwferu-densha-0.9.17/vendor/openwfe/expressions/fe_cancel.rb:100:in
> > `apply'
>
> Hello Tomaso,
>
> I've dug a bit, Ruote 0.9.18 is immune to that problem with the
> concurrent-iterator.
>
> You can fix it in 0.9.17 by modifying
> lib/openwfe/expool/expressionpool.rb cancel_process() method :
>
> Change the first line of the method
>
> ---8<---
> wfid = extract_wfid exp_or_wfid, false
> --->8---
>
> to
>
> ---8<---
> wfid = extract_wfid exp_or_wfid, true
> --->8---
>
> To make sure the parent process 20080523-gutzupuguri and not the
> sub-process 20080523-gutzupuguri.1 gets cancelled.
>
> I will make sure that expressions that use "sub process ids" don't
> become troublesome for the next 0.9.19. This issue was fixed by the
> changes announced in
>
> http://groups.google.com/group/openwferu-users/browse_frm/thread/58850b3103100982#
>
>
> I hope this will help, best regards,
>
> --
> John Mettraux - http://jmettraux.wordpress.com
>
> >
>


-- 
www.amicidelballoliscio.it

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenWFEru users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to