[Exist-open] Sanity check on 'update replace'

[Gary L. <gar...@en...>]

Hi all,

 

I've run into an exception on rare occasions running 'update replace'.  Both
the application and exist logs are reporting the error.

 

The update is definitely not done on the root element as reported.  The
eXist log seems to show there is some db corruption which may be the case,
but the resource was freshly loaded so I'm wondering if it could be an
'update' issue.

 

I'm using revision 1.2.4-8159.   Have there been any fixes since then that
address any issues similar to this?

 

Not sure if it matters but the database is fairly large: ~11Gb.

 

Thanks,

gary

 

 

Application log:

 

ERROR [http-8080-Processor15] sitemap.handled-errors 2009-01-15 09:24:46,558
- Error calling flowscript function main

            at
file:/D:/netvisn-server_V2/webapps/netvisn/site/flow/main.js:463:-1

.

Caused by: com.envisn.nv.exception.XdbException: errorCode:1; nested
exception: 

org.xmldb.api.base.XMLDBException: The root element of a document can not be
replaced with 'update replace'. Please consider removing the document or use
'update value' to just replace the children of the root. [at line 1, column
210]

 

eXist log:

 

2009-01-15 09:24:46,449 [http-8080-Processor15] WARN  (DOMFile.java
[get]:1482) - org.exist.storage.btree.BTreeException: node 1.6 not found. 

2009-01-15 09:24:46,449 [http-8080-Processor15] WARN  (SanityCheck.java
[showTrace]:93) - Stacktrace:

org.exist.util.sanity.AssertFailure: TRACE: Node 9225:1.6 not found.

            at org.exist.util.sanity.SanityCheck.TRACE(SanityCheck.java:72)