On 11/13/06, Boris Kraft <[EMAIL PROTECTED]> wrote: > > The error I get is "pre-apply failed", see end of this email. > > After restart of openwfe, things work again. The irritating thing is > that so far I have been unable to reproduce this. Initially I thought > this happens if my library workflow definition is not available upon > engine startup, but it seems that this is not the problem. I have > started up successfully without the library available, then made the > library available, and then successfully launched a flow that uses > library definitions. So its looks as if the engine checks for lib file > availability at various stages through its life time.
Hi Boris, the analysis seems fine. 1). is only this 'translate' subprocess concerned ? Are other missing subprocesses causing this "preapply failed" ? 2). is the "translate" string used as a variable name in some other flow ? (i.e. could the translate variable get unbound at engine level due to something like <unset variable="//translate" />, just an hypothesis). 3). could I have a look at the "engine environment" as stored on the disk ? (It should be somewhere at the root of the expression pool with a well recognizable name). The expression as stored for your production env would be perfect. Best regards, -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
