[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1

[Prabhat Jha (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12389374 ] 
            
Prabhat Jha commented on JBWS-1860:
-----------------------------------

Please help me understand it a bit.  ThreadLocal.remove is what you are using to fix memory leak, correct? When you say "these tests actually test ThreadLocal.remove", I am assuming you mean that when tests run, on server side, the code execution goes through the call ThreadLocal.remove, correct?

Ideally, this patch should work with both jdk1.4 and jdk1.5. Can you not quickly do a retro translation  on ThreadLocal? I know that Paul Gier has been working on adding more classes to retro project.

I will confirm with Ryan as well to see if will be okay just to have it working with jdk1.4.

> Memory leak fixes for JBossWS1.2.1
> ----------------------------------
>
>                 Key: JBWS-1860
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1860
>             Project: JBoss Web Services
>          Issue Type: Support Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jbossws-1.2.1
>         Environment: JBoss Application Server 4.0.5 + JDK1.5
>            Reporter: Magesh Kumar B
>         Assigned To: Prabhat Jha
>            Priority: Critical
>         Attachments: jbossws-client.jar, jbossws-core.jar
>
>          Time Spent: 2 days, 30 minutes
>  Remaining Estimate: 0 minutes
>
> Port the following memory leak fixes for JBossWS1.2.1
> [JBWS-1833] - ConfigObserver was causing a memory leak
> [JBWS-1903] - DOMUtils doesn't clear thread locals

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira