Hi Daniel, We resolved the ever-growing DocumentImpl. This issue turned out to be in one of our interceptors where we were using cloneNode(true) rather than importNode and the main DocumentImpl was acquiring copy after copy of the WSDL claimType nodes.
We are still, however, experiencing the issue with many DocumentImpl objects being created (they turn out to be SecurityToken objects) and kept indefinitely. For our purposes, we have need of multiple proxies, which I believe it is documented somewhere that this issue might exist in this scenario. Is there any documentation or thoughts on how to avoid having these extra SecurityToken objects remain in the MemoryOnlyTokenStore indefinitely (or at least seemingly so)? Thanks, Dan. -- View this message in context: http://cxf.547215.n5.nabble.com/Potential-Memory-Leak-tp5735592p5735750.html Sent from the cxf-user mailing list archive at Nabble.com.
