Something could be ending your HTTP session, while your browser is holding onto a cookie with the expired transaction information.
https://docs.marklogic.com/guide/app-dev/transactions#id_37297 Is there a use case that you have for carrying a transaction over multiple calls? The transaction mode of query changes you over to multi-statement transaction which need an explicit xdmp:commit() to end a transaction despite in only being a query. Unless you have a good reason not to, you could just add xdmp:commit() to the end of your code. https://docs.marklogic.com/guide/app-dev/transactions#id_68542 As you make changes you may need to clear your cookies to truly know if your changes fixed the problem. -Ryan On Fri, May 9, 2014 at 10:58 AM, William Sawyer <wilby.saw...@gmail.com>wrote: > When I set update to false and transaction-mode to query on page it causes > the page to error on everything other request. Has anyone else seen this > and know how to fix it? > > Thanks, > -Will > > declare option xdmp:update "false"; > declare option xdmp:transaction-mode "query"; > > 500 Internal Server ErrorXDMP-NOTXN: No transaction with identifier > 295241064692587278[1.0-ml] > > ML: 7.0-2.3 > OS: Windows 7 > Single Host > > _______________________________________________ > General mailing list > General@developer.marklogic.com > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
