On 11/14/06, Boris Kraft <[EMAIL PROTECTED]> wrote: > > > John Mettraux wrote: > > I would suggest a small test : > > > > 1). stop the suite > > 2). comment out the library loading component (out of > > etc/engine/engine-configuration.xml) > > 3). make sure by yourself that the "//translate" command (and others) > > is (are) present in the engine env .xml > > 4). restart the engine > > 5). launch a flow to see if translate & co are found
> What if the engine env is removed? I noticed that it gets recreated > automatically. Indeed. > I know that I have removed the environment once > intentionally. Also, I realize that until recently, the lib was not > loaded through library.xml but in fact must have been present in the > engine env due to the fact that the corresponding subprocess was called > at the launch of some prior workflow. In other words, here is what must > have happened so far > > * initially, I called a subflow (init) to define subprocesses when I > launched a "main" flow. > * at some time I removed the call to init, because I was under the > assumption that it was loaded as a lib, and in fact this was working > (it loads the stuff from the engine env) > * recently I discovered out of the blue (no changes nor problems for 2 > months) the "preApply failed" message and lost workflows. Was the hard reboot episode the starter for all of this ? 2 months of quietness and then now this serie of missing subprocesses... That's so strange. > * I found out that the init-flow was neither loaded by library.xml nor > a main flow. I did the following: restarted the engine, then launched a > new main flow, and got the "preApply failed" message > * I added the call to the init-flow in library.xml > * I tested again with the launch of a new flow, and things worked, so I > though all is fine now. > > Alas, I was wrong. Not all is fine, I still get the "preApply failed" > at various times, sometimes when launching, sometimes later. Once the > variables are unbound, everything else will fail, so I have to restart > the engine to make things work again. Another workaround would be not to use the library.xml and to really > As I said, this seems to affect all subprocess definitions defined in > my init-flow, not just the "translate". That's somehow comforting, it's a library problem then. > As a sidenote, I am an 1.7.2.pre0 I'll have a look at the changelog, to see what could potentially be involved. 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 -~----------~----~----~----~------~----~------~--~---
