[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143753#comment-16143753 ] 

Leandro Quiroga commented on WSS-614:
-------------------------------------

Thanks Colm, I've seen the WSSConfig.cleanUp() at https://github.com/apache/wss4j/commit/ab7ce2f6ec40e865f00efcd86e344f95db733acb, it would be nice if the clean up is done automatically at undeploy / finalize but this is a valid option. Don't you have in wss4j a hook to make the clean up?

I don't understand why you tagged this as Not A Problem if you made a resolution.

> org.apache.ws.security.transform.STRTransformProvider leak
> ----------------------------------------------------------
>
>                 Key: WSS-614
>                 URL: https://issues.apache.org/jira/browse/WSS-614
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Core
>    Affects Versions: 1.6.19, 2.0.10, 2.1.10
>         Environment: Java 1.8.0_131
> JBoss EAP 6.4.1
>            Reporter: Leandro Quiroga
>            Assignee: Colm O hEigeartaigh
>              Labels: leak
>         Attachments: STRTransformProvider leak.jpg
>
>
> A memory leak occur when undeploying a web application that uses WSS4J.
> The org.apache.ws.security.transform.STRTransformProvider is appended to java.security.Security at initialization in org.apache.ws.security.WSSConfig.init() but never removed.
> I've tested in wss4j-1.6.17 but I think it is the same in 1.6.19, 2.0.10 and 2.1.10.
> I've attached a screenshot of Eclipse MAT showing the leak.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org