Re: Potential Memory Leak

[Colm O hEigeartaigh <co...@apache.org>]

The Crypto objects should be cached in that manner to avoid loading them
per-invocation. Are you saying that it is repeatedly loading them + storing
them per-invocation?

Colm.


On Wed, Oct 30, 2013 at 6:44 PM, DTaylor <Da...@merge.com> wrote:

> 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.
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Potential Memory Leak

[Colm O hEigeartaigh <co...@gmail.com>]

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 <Da...@merge.com> 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.
>

Re: Potential Memory Leak

[DTaylor <Da...@Merge.com>]

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.