xdb:update

> Hi Guys
>  
> Is there are a known problem with xdb:update and eXist? I'm running the
> latest version of eXist externally.
>  
> I have a few end users who are accessing a form solution (a bit like DMV
> forms) simutaneously and occasionally I get:
>  
> java.lang.ArrayIndexOutOfBoundException
>  
> The result is the form detail they are trying to save gets corrupted and
> lost. I'm saving everything to file along the way and there is nothing
> out of the ordinary there, all seems fine. I've been through various
> re-writes etc trying to pin the problem.
>  
> Anyway, is there some config for:
>  
>  <p:processor name="oxf:xmldb-update">
>  
> ..to explicitly state locking, or protected write access? I'm pretty
> sure that the problem is around this...
>  
> Please help, I'm getting a real kickin' of my client.
>  
> Thanks
> Lee
>
>    
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

> Lee,
>
> Who throws the ArrayIndexOutOfBoundException, OPS or eXist? You should
> be able to figure this out by looking at the stack trace.
>
> Anyway, eXist would be in charge of handling multiple concurrent
> accesses, although it is hard to completely exclude that OPS is doing
> something wrong.
>
> I don't know of any parameters you can pass to eXist via XML:DB to
> control that behavior, but you may want to ask this on the exist-open
> mailing-list - and it would be great if you could report the results
> back to ops-users!
>
> -Erik
>
> Lee Bamford wrote:
>> Hi Guys
>>
>> Is there are a known problem with xdb:update and eXist? I'm running the
>> latest version of eXist externally.
>>
>> I have a few end users who are accessing a form solution (a bit like DMV
>> forms) simutaneously and occasionally I get:
>>
>> java.lang.ArrayIndexOutOfBoundException
>>
>> The result is the form detail they are trying to save gets corrupted and
>> lost. I'm saving everything to file along the way and there is nothing
>> out of the ordinary there, all seems fine. I've been through various
>> re-writes etc trying to pin the problem.
>>
>> Anyway, is there some config for:
>>
>>  <p:processor name="oxf:xmldb-update">
>>
>> ..to explicitly state locking, or protected write access? I'm pretty
>> sure that the problem is around this...
>>
>> Please help, I'm getting a real kickin' of my client.
>>
>> Thanks
>> Lee
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>

> Lee,
>
> Who throws the ArrayIndexOutOfBoundException, OPS or eXist? You should
> be able to figure this out by looking at the stack trace.
>
> Anyway, eXist would be in charge of handling multiple concurrent
> accesses, although it is hard to completely exclude that OPS is doing
> something wrong.
>
> I don't know of any parameters you can pass to eXist via XML:DB to
> control that behavior, but you may want to ask this on the exist-open
> mailing-list - and it would be great if you could report the results
> back to ops-users!
>
> -Erik
>
> Lee Bamford wrote:
>> Hi Guys
>>
>> Is there are a known problem with xdb:update and eXist? I'm running the
>> latest version of eXist externally.
>>
>> I have a few end users who are accessing a form solution (a bit like DMV
>> forms) simutaneously and occasionally I get:
>>
>> java.lang.ArrayIndexOutOfBoundException
>>
>> The result is the form detail they are trying to save gets corrupted and
>> lost. I'm saving everything to file along the way and there is nothing
>> out of the ordinary there, all seems fine. I've been through various
>> re-writes etc trying to pin the problem.
>>
>> Anyway, is there some config for:
>>
>>  <p:processor name="oxf:xmldb-update">
>>
>> ..to explicitly state locking, or protected write access? I'm pretty
>> sure that the problem is around this...
>>
>> Please help, I'm getting a real kickin' of my client.
>>
>> Thanks
>> Lee
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>

> I think it is worthing noting that eXist has had a bit of a overhaul in
> the shape of eXist 1.1-newcore, from the eXist site (
> http://exist.sourceforge.net/ ) :
>
> "..Based on the new indexing core. Represents a major technological
> switch with respect
> to the index system. All other areas (including most of the query
> engine) are identical
> to the 1.0 release. If you know eXist and had problems with too
> large/too complex documents
> or slow updates, try this version. "
>
> So anyone who had strange corruption issues with large documents etc it
> might be worth a try.