Re: [ruote:3766] Re-applied expressions getting stuck in "cancelling"

[John Mettraux]

On Wed, Aug 15, 2012 at 10:26:52AM -0700, Chris Conley wrote:
>
> Any ideas off the bat?

Hello Chris,

welcome on the mailing list (thanks for your previous feedback and
contributions via the issue tracker).

I've looked at your expressions.txt and reconstructed a flow that looks like:

---8<---
define
subprocess tasklet

define tasklet
cursor
subprocess work <--- here

define work
cursor tag: work2
--->8---

Are you re-applying at "subprocess work"?

Going on with the investigation, just wanted to know if my reconstruction
made sense.


Cheers,

--
John Mettraux - http://lambda.io/jmettraux

[John Mettraux]

Hello Chris,

I've set up a test repo at:

https://github.com/jmettraux/for_chris_reapply

Unfortunately, I cannot reproduce the issue, the re_applying happens as
expected.

Is there a way for you to fork this repo and make it fail (reproduce the
issue in it)?

Could it be an issue with one of your participant implementation (missing
cancel / on_cancel)?


Thanks in advance,

[Chris Conley]

Hi John,

So sorry for the delay; I missed any notifications from the mailing list. In any case, thanks very much for the reply.

It's been a while since I dove into this, but I'll be looking into it again in the next few days and will let you know if I can re-create the issue in the repo you set up.

Thanks!

Chris

[Chris Conley]

Hi John,

I still haven't had a chance to dive into this, but I was wondering if there was a way to just completely wipe a process from Ruote?

The details for a process that I tried to kill last week are here: https://gist.github.com/fd0868d71240a4f305a7

Is there away way to remove that directly from memory since it seems to be getting stuck in the dying state?

Thanks!

Chris

[John Mettraux]

On Wed, Oct 17, 2012 at 01:12:33PM -0700, Chris Conley wrote:
>
> Is there away way to remove that directly from memory since it seems to be
> getting stuck in the dying state?

Hello Chris,

ruote 2.3.0 has the Dashboard#remove_process(wfid) method. It should remove
all the pieces (expressions, schedules, tracker entries, ...) composing a
workflow instance.

Thanks for sharing the gist, I'll take the time to look at it, maybe there is
a hint for me in there.


Best regards,

[Mario Camou]

Hi,

I've found that, at least through the RuoteKit console, I have to kill processes twice to actually make them go away, after the first time the expressions column shows up as empty and I have to go in and kill them again.

Cheers,
-Mario.

On Nov 13, 2012 9:15 AM, "Ranaldo Bowker" <ranaldo...@gmail.com> wrote:

Hi everyone,

Im currently having a similar problem, where I cannot remove/kill processes.

I have a lot of stale processes, when ever I try to kill ( RuoteKit.engine.kill_process(wfid) ), or cancel them they just remain there,
I've noticed as well, when viewing the processes in RuoteKit, the position column is empty.

Im using Ruote 2.2.0

Any help would be greatly appreciated,

Thanks
Ranaldo

--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to openwfe...@googlegroups.com
to unsubscribe : send email to openwferu-use...@googlegroups.com
more options : http://groups.google.com/group/openwferu-users?hl=en

[John Mettraux]

> On Nov 13, 2012 9:15 AM, "Ranaldo Bowker" <ranaldo...@gmail.com> wrote:
> >
> > Im currently having a similar problem, where I cannot remove/kill
> > processes.
> >
> > I have a lot of stale processes, when ever I try to kill (
> > RuoteKit.engine.kill_process(wfid) ), or cancel them they just remain there,
> > I've noticed as well, when viewing the processes in RuoteKit, the position
> > column is empty.
> >
> > Im using Ruote 2.2.0
> >
> > Any help would be greatly appreciated,
> >
On Tue, Nov 13, 2012 at 09:19:56AM +0100, Mario Camou wrote:
>
> I've found that, at least through the RuoteKit console, I have to kill

> processee twice to actually make them go away, after the first time the

> expressions column shows up as empty and I have to go in and kill them
> again.

Hello Ranaldo,

I don't know what your processes look like so I don't know what the cause of
for those stale processes.

Now in order to get rid of them, Ruote 2.2 hasn't got the #remove_process
method so, if Mario's suggestion doesn't work, there's more work ahead.

In your ruote initializer add the following code:

---8<---
module Ruote
module StorageBase
def remove_process(wfid)
# ...
end
end
end
--->8---

where the body of the method is detailed at:

https://github.com/jmettraux/ruote/blob/b5b58906060ef2bedffb4f93f0587421a4e7b836/lib/ruote/storage/base.rb#L274-297

Then you'll have to call that method for each wfid (process instance id) for
the stale processes.

If that doesn't work, please explain how it doesn't work (remember I need
details, saying "it doesn't work" is a waste of time for both of us).

(and if that really doesn't work, we'll fallback to manual removal of all
documents composing the stale process instances)

[Ranaldo Bowker]

Hi John,

The remove_process method worked like a charm...

Thanks a mill, appreciate your help.

Kind regards
Ranaldo