Memory leak using smooks ------------------------ Key: JBESB-2520 URL: https://jira.jboss.org/jira/browse/JBESB-2520 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 There is a SOA memory leak issue logged against the jbr-provider but the impact would appear, at first glance in any case, to be more pervasive than this. I added the following comment to SOA-1283 "A quick look at the profiler output would suggest that the following may be the cause of the leak. Each request results in a new WSSecurityInfoExtractor being instantiated which, in turn, creates a new Smooks instance. Each Smooks instance results in a new StandaloneApplicationContext which in turn instantiates SmooksResourceConfigurationStore. One leak, from a cursory inspection, would appear to be due to SmooksResourceConfigurationStore. During the construction of this class it will register a shutdown hook but this is never cleaned up, resulting in a hard reference to the SmooksResourceConfigurationStore. Other instances of this issue would appear to be present in AbstractStreamSplitter, SmooksHandler, SmooksMapper and SoapUIClientService. A quick fix would be to disable the shutdownHook for every instance of Smooks being created but the whole creation of the Smooks instance would appear to be heavyweight and it would be a better solution to handle this in a less resource intensive manner. The modification would be something like the following smooks.getApplicationContext().getStore().removeShutdownHook();" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira