Julie McCabe wrote:
Hello,
Resolution: I upgraded to the latest version of xindice from CVS.
LOL! That's a good one :-)
Vadim
Thanks Julie.
On Tuesday 09 March 2004 14:32, Terry Rosenbaum wrote:
Sorry, I don't know if first/second invocation makes a difference or sheds any light. But, I do know that Xindice 1.0 is full of bugs, and nobody is fixing that version. The latest version in CVS is still being actively worked on.
I strongly recommend using the latest version from CVS.
-Terry
Julie McCabe wrote:
Hello,
Thanks for the quick response. I think this may be contributing but the first time I perform this query using Java it works but the second time it gets the out of memory error. If is because the Strings are too long then it should fail every time? Do you think there might be a memory leak somewhere?
Many thanks, Julie.
On Tuesday 09 March 2004 14:09, Terry Rosenbaum wrote:
83K * 20 in one String perhaps overflows the memory allowed your VM. See
http://marc.theaimsgroup.com/?l=xindice-users&m=107604913129099&w=2 <http://marc.theaimsgroup.com/?l=xindice-users&m=107604913129099&w=2>
May be able to get it to do what you want by passing the VM args to increase memory limit.
-Terry
Julie McCabe wrote:
<>Hello,
I am using xindice 1.0 on linux Red hat 9, tomcat 4.1.27. I have 20
documents each of size 83k in a collection. When I use the command line
xindice xpath -c /db/config -q "/"
it prints all the documents out.
However when I perform the same xpath query using java I can perform it
once and then after I get a java.lang.OutOfMemory error. Any ideas why
this is? I am using the method getContentAsDOM in XMLResource to
retrieve the documents.
Thanks Julie
