Re: [Exist-development] Errors from Stress tests on xquery update

[Casey J. <cas...@jo...>]

Wolfgang,

Thanks. I will test this workaround. So would you consider this to be a bug
that will be eventually fixed in eXist, or will developers always need to
be aware of this when using the update methods?

Thanks,

Casey

On Wed, Jul 18, 2012 at 2:18 PM, Wolfgang Meier <wol...@ex...>wrote:

> Hi Casey,
>
> the NullPointerException in your logs occur after the corresponding
> documents have been locked. It thus seems the locking did fail or miss
> some nodes for unknown reasons and the update tried to operate on a
> node which was deleted.
>
> To avoid such issues, it might help to explicitely put a lock on the
> documents before you start the actual modifications. There's a
> (pseudo-) function: util:exclusive-lock($nodes as node()*, $expression
> as item()*) item()*. It takes a sequence of nodes from documents to be
> locked and acquires an exclusive lock before it executes the code
> block given in $expression.
>
> Wolfgang
>



-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.