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

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

I will add the test to the eXstress github, this is the only way I know how
to reproduce this. Although it may be possible to use timers to achive the
same result. IE: Running two threads in parallel that both select out nodes
to be operated on. Then one thread waits 500ms and removes the nodes, and
the other waits 1500ms to perform it's operation.

I would assume this could create the same situation.

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

> > 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?
>
> There seems to be a bug. eXist does allow dirty reads, which means it
> is possible for node references to become invalid during a query.
> Nevertheless a started transaction must not abort.
>
> I have received another test from someone else which fails for similar
> reasons. We have to figure out what causes this. It's not easy though.
> If you have a reproducible test, I'll be happy to compare it to the
> other scenario I have.
>
> 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.