[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2461) Request / Response Resource Optimisation

[Alessio Soldano (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBWS-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-2461:
----------------------------------

    Fix Version/s: jbossws-native-3.2.1
                       (was: jbossws-native-3.2.0)


> Request / Response Resource Optimisation
> ----------------------------------------
>
>                 Key: JBWS-2461
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2461
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions: jbossws-native-3.0.5
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: jbossws-native-3.2.1
>
>
> There are a few points where the management of resources can be optimised, in these places we are relying on a few techniques that are leading to potential leaks.
> The first area to optimise is the use of ThreadLocals for DocumentBuilders etc - these should be optimised to be better related to the request / response.
> A second area relates to SwapableMemoryDataSource - something is needed to clean up files not automatically deleted from killed / crashed JVMs.  Secondly relying on finalize to delete the files can lead to a large number of files on disk before GC especially with large heaps.  Ideally these will be better associated with the current request to be cleaned up at the end of processing.
> Although these are two different problems I have grouped them together as the common problem is tracking resources with the request they really belong to.

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