Hi Alex, Alexander Klink wrote: >> Looks like OpenXPKI's Persister module has problems >> with handling of the time. We have just tried today's patch >> of Jim Brandt for persister part of the Workflow module, and >> this patch does not change anything related to our picture. >> Nonetheless this patch looks very much like really related to >> our problem, but we do not understand how use this knowledge >> to fix the problem. >> > Does it? I believe it deals with date/time formats, so I don't > really see how this is related to what we do ...? We even do the > time handling ourself in our DBI persister. >
Not that simple. Before this patch "current time" was set only once: near the beginning of the Workflow's persister module. Then it was used several times. Hence near the end of the module "current time" pointed to the past, which hampered the main sense of persister operation. And could let to the conflict very similar to our problem. If OpenXPKI's persister module employs somewhat similar timing policy (I failed to understand this), then this could lead to timing problems too. The patch of Jim Brandt sets "current time" anew each time when it is used. All the best, Sergei ------------------------------------------------------------------------- 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
