Rob Redmon wrote:
Maybe this isn't a question for here, I guess maybe it's more of something I need to learn about xpath or the xmldb API.
I've been running into OutOfMemory exceptions when the result of an xpath query (via the Java API) is going to be fairly large (probably the result would be a few MB if stored as a xml text file) and so I'm wondering if there is some better tuning that I can do or better useage of XpathQueryService...
First of all, avoid large files (see FAQ). If you can't live without large files (can't refactor into small files), please keep in mind that Xindice needs to have whole file in-memory in order to work on it (xupdate, xpath, etc). This means, that you have to give server enough memory (java options -Xmx, -Xms) to keep necessary amount of such documents in memory.
Vadim
