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

Magesh Kumar B (JIRA) jira-events at lists.jboss.org
Tue Nov 27 01:00:18 EST 2007


     [ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ]

Magesh Kumar B updated JBWS-1860:
---------------------------------

    Patch Instructions: 
PATCH NAME: 
        JBWS-1860 
PRODUCT NAME: 
        JBossWS
VERSION: 
        1.2.1.GA
SHORT DESCRIPTION: 
        Memory leak fixes for JBossWS. 
LONG DESCRIPTION: 
        This patch contains fixes for the following memory leak issues 
         1 - ConfigObserver was causing a memory leak 
         ConfigObserver becomes a possible memory leak through the Observable pattern that's used between EndpointMetaData(Subject) and CommonBindingProvider(Observer) 
         2 - DOMUtils doesn't clear thread locals 
         DOMUtils doesn't clear thread locals hence it causes Memory Leaks. 
MANUAL INSTALL INSTRUCTIONS:
 These instructions assume you have already successfully installed JBossWS 1.2.1.GA and are updating the installation. 

        This patch is only applicable for the Java 5.0 version: - 
        1.Copy the attached jbossws-client.jar file over the existing one in %JBOSS_HOME%/client.
        2.Copy the attached jbossws-core.jar file over the existing one in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jbossws.sar. 

        For JDK1.4 please use the unpatched version of JBossWS1.2.1.GA
COMPATIBILITY: 
        None 
DEPENDENCIES: 
        JBossWS1.2.1.GA 
SUPERSEDES: 
        None 
SUPERSEDED BY: 
        JBossWS2.0.1SP2
CREATOR: 
        Magesh Kumar B 
DATE: 
        16th November 2007

  was:
PATCH NAME: 
        JBWS-1860 
PRODUCT NAME: 
        JBossWS
VERSION: 
        1.2.1.GA
SHORT DESCRIPTION: 
        Memory leak fixes for JBossWS. 
LONG DESCRIPTION: 
        This patch contains fixes for the following memory leak issues 
         1 - ConfigObserver was causing a memory leak 
         ConfigObserver becomes a possible memory leak through the Observable pattern that's used between EndpointMetaData(Subject) and CommonBindingProvider(Observer) 
         2 - DOMUtils doesn't clear thread locals 
         DOMUtils doesn't clear thread locals hence it causes Memory Leaks. 
MANUAL INSTALL INSTRUCTIONS:
 These instructions assume you have already successfully installed JBossWS 1.2.1.GA and are updating the installation. 

        If you require the Java 1.4 version: - 
        1.Copy the attached jbossws14-client.jar file over the existing one in %JBOSS_HOME%/client.
        2.Copy the attached jbossws14-core.jar file over the existing one in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jbossws.sar.

        If you require the Java 5.0 version: - 
        1.Copy the attached jbossws-client.jar file over the existing one in %JBOSS_HOME%/client.
        2.Copy the attached jbossws-core.jar file over the existing one in %JBOSS_HOME%/server/%SERVER_CONFIG%/deploy/jbossws.sar. 
COMPATIBILITY: 
        None 
DEPENDENCIES: 
        JBossWS1.2.1.GA 
SUPERSEDES: 
        None 
SUPERSEDED BY: 
        JBossWS2.0.1SP2
CREATOR: 
        Magesh Kumar B 
DATE: 
        16th November 2007


> 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
>            Reporter: Magesh Kumar B
>         Assigned To: Magesh Kumar B
>            Priority: Critical
>         Attachments: jbossws-client.jar, jbossws-core.jar, jbossws14-client.jar, jbossws14-core.jar
>
>          Time Spent: 1 day, 3 hours, 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

        



More information about the jbossws-issues mailing list