Hi Dan, This may have been fixed in a more recent version of CXF/WSS4J. If you are concerned about the constant creation of new Crypto objects per-thread, have you considered just creating it once + supplying the object as a reference to CXF/WSS4J? For example, for the WS-SecurityPolicy approach you can pass a Crypto Object in via the "ws-security.signature.crypto" tag for Signature + "ws-security.encryption.crypto" tag for Encryption. Similar tags exist for the older "Action" based approach of configuring WS-Security.
Colm. On Mon, Nov 4, 2013 at 2:24 PM, DTaylor <[email protected]> wrote: > Hi Colm, > > Our user is creating a thread per invocation. This new thread causes a new > crypto object to be created. This is with CXF 2.6.2, however, so the issue > may have been fixed in a later release which we have not been able to move > to as of yet. Is this the case? > > Thanks, > > Dan. > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Potential-Memory-Leak-tp5735592p5735913.html > Sent from the cxf-user mailing list archive at Nabble.com. >
