The thing to know is that XDMP-EXTIME cannot be caught by the query that caused it. Since the state advancement in CPF is handled in the calls to cpf:success and cpf:failure in the body of the action itself, the state cannot be advanced in this case and you won't get the cpf:error property set either. (CPF works this way so that the state of the document as recording in the properties is not in a separate transaction from the changes made to the document, so that the document and its step stay in sync.)
So the first problem you have is: why is XDMP-EXTIME being thrown in the first place. I would suggest running/profiling your code in Query Console. Your second problem is the 500 error. It is hard to know what to do about that problem is without knowing the specific error. //Mary > I have a situation where Timeout exception(XDMP:EXTIME) occurs in CPF > and document neither enters the error state, nor advances to the next > state and the status of the cpf remains in "active". Reinsertion of the > document fails with a 500 internal server error. > > I tried to change the state and status of the cpf properties but was > unable to do so, neither I am able to delete the document. Any action > that I try to perform on this document gives me back XDMP:EXTIME.can > anyone comment on why would this happen. > > Also will restarting the Marklogic server change the state to initial? I > believe CPF will restart from where it left off on restarting the > server.This happens only in Production . I am not able to replicate the > same issue in Dev or QA/Test. > > Can anyone comment on why would this happen and is their is a way I > could Modify the CPF Status or delete the document. Any help on this is > appreciated. > > I did go through this post and tried few options, but of no help. > http://community.marklogic.com/pipermail/general/2010-March/005011.html > _______________________________________________ General mailing list [email protected] http://community.marklogic.com/mailman/listinfo/general
