Hi Alan, I read the ticket, does this mean that it is fixable in a later release of the Xalan library or get aroundable in some other way.
Is there an OpenBD ticket I can watch in some way ? Is the temp fix you refer to accessible in the nightly build ? Due to the insane number of xpath queries we can make in a request it's a show stopper for us currently but I if I can watch a ticket then I can resume my openbd testing as and when. Many thanks Alex On Feb 6, 1:17 pm, "Alan Williamson (aw2.0 cloud experts)" <[email protected]> wrote: > Right the good news is that i have found the problem. > > it is inside the XPATH library. it adds a reference to the original > Node object for any call backs. there is no way to clear those. > > There is a bug report opened on it: > https://issues.apache.org/jira/browse/XALANJ-1673 > > In the meantime, i have manually cloned the node before passing it on. > While this will use more memory in that given request, it will keep > overall usage down. > > This is just a temp fix; we'll update the XALAN library (probably just > use the 1.5 that comes with Java instead of a separate library). But i > do not have time to do this just now, as i am preparing stuff for > OpenCFSummit. -- tag/function ref: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
