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/
