Hi all,
On Wed, Jun 27, 2007 at 06:14:45PM +0200, Alexander Klink wrote:
> > The reason according to logs is that two opposite conditions
> > ( wf_child_instance_finished and !wf_child_instance_finished )
> > both appears to be valid. I cannot figure out why it happens.
> > It happens rather often.
> Same here. I've debugged it a few hours today and have some leads,
> but unfortunately nothing worked out yet. I guess I'll have to sleep
Good news: Martin and I figured out why it happens today. It was
actually a bug in Workflow, which has been introduced by yours truly ...
I've patched Workflow earlier to delete the condition cache so that the
result is not cached "forever", but apparently I've deleted it at the
wrong time (everytime someone calls 'evaluate_action' on a workflow state).
I guess this was not noticed in the "normal" workflows because they
were using the "may_stop" option and just stopped when something
similar happened (and were manually restarted) ...
I've prepared a patch for Workflow which I just checked into the
Workflow SVN repository and hopefully Jonas will be able to prepare
a new Workflow release soon.
Sorry for the inconvenience :-( ...
Best regards,
Alex
--
Dipl.-Math. Alexander Klink | IT-Security Engineer
[EMAIL PROTECTED] | working @ urn:oid:1.3.6.1.4.1.11417
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
