[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143791#comment-16143791 ]
Colm O hEigeartaigh edited comment on WSS-614 at 8/28/17 1:47 PM: ------------------------------------------------------------------ No there is no hook there at present. If you want to look into adding one, then patches are welcome. The cleanUp method that was added is not really a "fix" as such. I'll change the tag to "workaround". If you want to look into providing a patch then feel free to re-open it. was (Author: coheigea): No there is no hook there at present. If you want to look into adding one, then patches are welcome. The cleanUp method that was added is not really a "fix" as such. I'll change the tag to "won't fix". If you want to look into providing a patch then feel free to re-open it. > 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-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org