Hi Petr,
> The new tests added in revision 978 are designed to help fixing the bug
> #1699848.
Thanks for this, it helps a lot in trying to figure it out.
> At the moment the test in the case of fail dumps:
> # $VAR1 = {
> # 'LIST' => [
> # {
> # 'LABEL' =>
> 'I18N_OPENXPKI_SERVICE_DEFAULT_COMMAND_EXECUTION_ERROR',
> # 'PARAMS' => {
> # 'ERROR' => 'State
> \'CHECK_CHILD_FINISHED\' should be automatically executed but there are
> multiple actions available for execution. Actions are: null2, null'
Same here (sometimes I also get no activity available errors).
> 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
over it ... One idea is that it is related to the workflow factories
that are inherited from the parent and thus the state objects might
be reused in the children and the condition cache emptied in between
checking the different conditions. Unfortunately, reinitializing the
workflow factories after forking did not help, so I'll have to look
in another direction next. From openxpki.log (I've enabled debug
output for Workflow) it looks like memory and database might not be
in sync, but I have not confirmed that yet.
Any ideas from your side are highly appreciated as well ...
Best regards,
Alex
Best regards,
Alex
-------------------------------------------------------------------------
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
