Hi John,
So some strangeness today:
I have a bit of process def that has this:
sequence :unless => '$f:machine.remote_id' do
I've encountered a scenario where this comparison fails - from my logs I
see a dump of f:machine that does have 'remote_id' populated just before
this process is run.
Somehow the sequence is still executed.
Note that this particular process is nested under a concurrent_iterator -
and in the other branches 29 other machines (properly) skipped this
sequence, but one did not.
I've looked over some of the older posts about comparisons, and I don't
think i'm doing anything too strange here.
Do you think this would be an issue with ruote-mon? ( which I'm still using
with 1 worker )
I haven't tried to replicate this issue using another storage.
I'm just now starting to attempt to replicate this issue with a simple test
case, but something tells me this isn't simple.
--Thanks
Matt York
On Thursday, February 6, 2014 4:01:17 PM UTC-8, John Mettraux wrote:
>
>
> On Thu, Feb 06, 2014 at 02:39:07PM -0800, Matthew York wrote:
> >
> > (...)
> >
> > goal was to provide some redundancy.
> > The processes queuing up work for ruote are behind activeMQ, so I
> suppose
> > there is still redundancy even if I end up splitting the 2 workers to
> use
> > separate storage.
> >
> > Rather than troubleshoot ruote-mon I was thinking about trying the redis
> > provider to see if it exhibits the same behavior.
> > For now I'll move ahead with a single worker & attempt to find whatever
> > other issues I may be having with the process definitions themselves.
> >
> > Later on if I want to continue to troubleshoot is
> > using http://ruote.rubyforge.org/noisy.html the only way to go? I
> recall
> > having issues trying to get this to work.
>
> Hello,
>
> I can't remember you mentioning having trouble with getting noisy to work
> ;-)
>
> I used(d) noisy a lot when developing expression and when debugging
> process
> definition. Along with test/rspec it's great to see what a worker is
> doing.
> When there are two workers working on the same process instance, the noisy
> output gets split, making it difficult to interpret without some
> shuffling.
>
> Best regards,
>
> John
>
>
--
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"ruote" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
