Hi Martin and Alex,
> > The patch of Jim Brandt sets "current time" anew each time when it
> > is used.
>
> Could you please point to a corresponding patch line?
These lines are concerned to the test file persister_dbi.t.
Jim fixed the problem which led to the behavior that was very
similar to our case: less time - test runs ok, more time - test fails.
Another sameness: this problem was in Persister like ours.
But maybe you are right and our problem is completely different one.
> > If OpenXPKI's persister module employs somewhat similar timing policy
> > (I failed to understand this), then this could lead to timing
> > problems too.
>
> If I am not totally mistaken then the persister should not cause any
> timing problems at all.
I will not insist that our problem is a timing one but the fact is:
if Persister on my machine works too long I get an error:
"Can't call method "fetch_workflow" on an undefined value at
/home/eva/prefix/ox/lib/perl5/site_perl/5.8.8/mach//OpenXPKI/Server/API/Workflow.pm
line 257"
This is because the function __get_workflow_factory in
OpenXPKI/Server/API/Workflow.pm line 254
returns nothing:
my $factory = __get_workflow_factory({
WORKFLOW_ID => $wf_id,
});
and $factory variable stays undefined.
Could Persister influence DB in such a way that __get_workflow_factory fails
later?
If not what could be a reason?
I really have no ideas :((
Best regards,
Julia.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
