Hi Lukas!
On Thu, Sep 12, 2013 at 10:59 AM, Lukas Loesche <[email protected]> wrote:
> Interestingly if I call Daemons.daemonize({ontop: true}) which will make
> it stay on top and not fork or detach from the terminal, than it works and
> the workflow executes.
>
> I also tried daemonizing the Process before launching the workflow but
> that didn't work either. Meaning the workflow launches and the wfid is
> written to the daemon log, but after that the first participant in the
> workflow isn't doing anything just like before.
>
> Any suggestions what I might be doing wrong or what I could try to better
> debug the problem?
>
> This is indeed a sticky situation... I have some suggestions that might
help.
First off, always do "Thread.abort_on_exception = true" so a an uncaught
exception kills your daemon, and not just the thread.
Secondly, you could use safely (
https://github.com/kennethkalmer/safely/wiki/Backtrace) to try and log a
backtrace for you when then daemon dies to see if there are possible
exceptions.
The only thing I can think off is that your participant possibly relies on
some IO object that got opened BEFORE daemonizing, and is no longer
available after daemonization...
If you could package the smallest possible example in a gist it would
greatly help us to debug the issue, including the contents of your Gemfile
(even if you're not showing us the code used by said gems).
Kind regards
--
Kenneth Kalmer
[email protected]
http://opensourcery.co.za
@kennethkalmer
--
--
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.
