Each application server has a request timeout (defaulting to 30 seconds). Assuming you're not trying to do a multi-statement transaction, your request has to finish before that request timeout is up. It sounds like your transaction is failing to get the requested lock in a timely manner. We would need more detail to have any idea why.
What I would look for: are other simultaneous transactions requesting a lock on the same URI? If so, the request that throws the error is probably getting hung up waiting for others. -- Dave Cassel<http://davidcassel.net>, @dmcassel<https://twitter.com/dmcassel> Technical Community Manager MarkLogic Corporation<http://www.marklogic.com/> http://developer.marklogic.com/ From: <[email protected]<mailto:[email protected]>> on behalf of "Mani, Sivasubramani (ELS)" <[email protected]<mailto:[email protected]>> Reply-To: MarkLogic Developer Discussion <[email protected]<mailto:[email protected]>> Date: Wednesday, February 3, 2016 at 1:37 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "Aroul, Pavadai Durai (ELS-CON)" <[email protected]<mailto:[email protected]>> Subject: [MarkLogic Dev General] Regarding Time limit exceed issue Dear Team, We get time limit exceed issue while executing the “xdmp:lock-for-update”. Kindly guide us how to getting rid from this. Thanks & Regards, Siva
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
