The xupdate implementation that Xindice uses isn't thread safe. The xupdate code uses a global static variable to hold temporary nodes. Their is also others cases where temporary elements can be left around but I haven't been able to get the patch commited on the xupdate side.
Todd Eickvonder Bjoern wrote: > I use b4 and it does occur if multiple users are manipulating different > documents in a collection via xupdates, especially those commands that append > elements. In that case sometimes some of the appended elements are missing or > a document contains elements that would normally belong to another document. > I tracked this issue a little bit and I think it is maybe somewhere in the > xupdate implementation, that is used, so it is not entirely an xindice > problem. > > Björn Eickvonder > > -----Ursprüngliche Nachricht----- > Von: Vadim Gritsenko [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 28. Juli 2005 16:33 > An: [email protected] > Betreff: Re: AW: Performance > > Eickvonder Bjoern wrote: > >>Moreover I had problems if multiple users are adding/writing >>(different) files to a collection concurrently (some data was later on >>corrupt or missing), so I had to synchronize the write access to each >>collection. > > > What xindice version did you use. I've not seen corruptions since b4. > > Vadim > > > > > ____________ > Virus checked by G DATA AntiVirusKit > Version: AVK 15.0.6273 from 27.07.2005
