Ok we've resolved this with the ehcache configuration... The one remaining leak we can see is that of Merlin crypto objects being placed into the WSHandler.cryptos hashtable.
Has anyone encountered an issue where the Crypto objects are being indexed by the Crypto.toString() value (e.g. the key is: RefId-org.apache.ws.security.components.crypto.Merlin@<memory address>)? Thanks, Dan. -- View this message in context: http://cxf.547215.n5.nabble.com/Potential-Memory-Leak-tp5735592p5735785.html Sent from the cxf-user mailing list archive at Nabble.com.
