[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh Kumar B updated JBWS-1860: --------------------------------- Summary: Memory leak fixes for JBossWS1.2.1 (was: Port JBWS-1833 - ConfigObserver was causing a memory leak to JBossWS1.2.1) Remaining Estimate: 4 days (was: 0 minutes) Description: 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 was:Port [JBWS-1833] - ConfigObserver was causing a memory leak to JBossWS1.2.1 -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh Kumar B updated JBWS-1860: --------------------------------- Attachment: jbossws-client.jar jbossws-core.jar jbossws14-client.jar -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12388678 ] Prabhat Jha commented on JBWS-1860: ----------------------------------- Just ran WS internal tests with jdk1.5 and that has 100% pass rate. Going to run the rest. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12389105 ] Prabhat Jha commented on JBWS-1860: ----------------------------------- Any update on this Magesh? -- 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

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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh Kumar B updated JBWS-1860: --------------------------------- Attachment: (was: jbossws14-core.jar) -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh Kumar B updated JBWS-1860: --------------------------------- Environment: JBoss Application Server 4.0.5 + JDK1.5 (was: JBoss Application Server 4.0.5) -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12389246 ] Magesh Kumar B commented on JBWS-1860: -------------------------------------- http://www.jboss.com/?module=bb&op=viewtopic&t=74785 JBoss Retro, does not support ThreadLocal implementation as of yet. * ThreadLocal These tests actually test ThreadLocal.remove() so we would need our own JDK1.4 impl to pass these tests (I removed the tests) -Courtesy Adrian (See post http://www.jboss.com/?module=bb&op=viewtopic&t=74785&postdays...) -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12389380 ] Prabhat Jha commented on JBWS-1860: ----------------------------------- Please read "I will confirm with Ryan as well to see if will be okay just to have it working with jdk1.4." in my previous comment as "..working with jdk1.5" -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=comments#action_12389517 ] Magesh Kumar B commented on JBWS-1860: -------------------------------------- Let me do this first then. -- 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

[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh Kumar B updated JBWS-1860: --------------------------------- Attachment: jbossws14-core.jar -- 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

[ 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. 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. 3. Copy the attached jbossretro-rt.jar file over the existing one in %JBOSS_HOME%/client. 4. Copy the attached jbossretro-rt.jar file over the existing one in %JBOSS_HOME%/server/%SERVER_CONFIG%/lib. 5. If you are running the test suite/samples test cases make sure the attached jbossretro-rt.jar and jbossretro.jar files are copied over the existing ones in thirdparty directory of the test suite/samples directory (This assumes you have already initiated the build by pulling in all the required thirdparty libraries) 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: 28th 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. 3. Copy the attached jbossretro-rt.jar file over the existing one in %JBOSS_HOME%/client. 4. Copy the attached jbossretro-rt.jar file over the existing one in %JBOSS_HOME%/server/%SERVER_CONFIG%/lib. 5. If you are running the test suite/samples test cases make sure the attached jbossretro-rt.jar and jbossretro.jar files are copied over the existing ones in thirdparty directory of the test suite/samples directory (This assumes you have already initiated the build by pulling in all the required thirdparty libraries) 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. 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 -- 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