Danny Sokolsky wrote: > If the spawned module processing takes longer then the time > limit, then that module will throw an exception (and it will > not complete).
Yes, that's what I understood. The question is: can we do anything to detect that? Let's take the example of a pipeline launched by the insertion of a document (yes, I know the pipeline itself is not "executed", but that's a good abstraction though). From what I understand, the installation of the pipeline creates a trigger on document insertion (which is pre-commit), and a trigger on property change (which is post-commit). The first trigger sets a property on the newly inserted document (setting its status to created), and that fires the second trigger, but only after the transaction has been committed (as a task if I am right). This second trigger in turn sets the state to "initial" and executes the module associated with that state. If this module does times out, then this transaction is rolled back, and the net effect is that even the state is not recorded on the document. If that is correct, I do not see any way to detect whether the state has succeeded or not (at least in case of a timeout). But maybe my understanding is simply not correct... > the API documentation for xdmp:spawn That's maybe the missing piece. Thanks for the link! Regards, -- Florent Georges http://www.fgeorges.org/ _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
