In situations such as these, I find it useful to log what is happening with
an expression like
xdmp:log(fn:concat ("position #1: xact (", xdmp:transaction(), "), mode (",
xdmp:get-transaction-mode(), "), ts (",xdmp:request-timestamp(),")")),
This will log the current transaction number, the transaction mode, and the
request timestamp (or empty for query statements).
/ch
On Tue, Sep 15, 2015 at 3:31 PM, Ignacio Tripodi <
[email protected]> wrote:
> Besides the obvious code analysis by simple inspection (which can prove
> less than simple on large, complex systems), is there a reliable way to
> tell if a request to MarkLogic produced an XQuery mutating operation
> anywhere during the lifetime of that request? I'm interested to analyze if
> a particular request would be causing a document update somewhere or not.
> I'm looking at lock rates in the monitoring charts, for example, but
> they're just rates and not linked to a particular request.
> Thanks for any insight you could provide,
>
> -i
>
>
> _______________________________________________
> General mailing list
> [email protected]
> Manage your subscription at:
> http://developer.marklogic.com/mailman/listinfo/general
>
>
_______________________________________________
General mailing list
[email protected]
Manage your subscription at:
http://developer.marklogic.com/mailman/listinfo/general
