It is logging the fact that there was a race condition between multiple triggers for the same document. If you only see it occasionally it is benign but when you see it for every document it is a sign that you may need to reconsider your application design. But yes it says that cpf is already processing or has already proceeded the document in that state as far as it can tell. The current state no longer matches the triggering state.
Sent from my Samsung Epic™ 4G Frank Rubino <[email protected]> wrote: Hi there- My modular document pipeline occasionally writes log lines like: Info: TaskServer: state is already successor so not updating for/products-expanded/988-24181-EA_modular_xml_expanded.xml I am speculating that CPF thinks it took care of this already. True? Frank This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, be aware that any disclosure, copying or distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please immediately return it to the sender and delete it from your system. Thank you _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
