Created: (JBWS-1860) Port JBWS-1833 - ConfigObserver was causing a mem

Thread: Created: (JBWS-1860) Port JBWS-1833 - ConfigObserver was causing a mem

Search this list only Search all lists
Created: (JBWS-1860) Port JBWS-1833 - ConfigObserver was causing a mem
United States	2007-10-21 23:04:03
Port JBWS-1833 - ConfigObserver was causing a memory leak to JBossWS1.2.1 ------------------------------------------------------------ ------------- Key: JBWS-1860 URL: http://ji ra.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 Reporter: Magesh krishna B Assigned To: Magesh krishna B Priority: Critical 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Updated: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-14 23:08:18
[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh krishna 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 > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 > Reporter: Magesh krishna B > Assigned To: Magesh krishna B > Priority: Critical > Time Spent: 4 hours > Remaining Estimate: 4 days > > 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-21 12:45:19
[ 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. > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Prabhat Jha > Priority: Critical > Attachments: jbossws-client.jar, jbossws-core.jar, jbossws14-client.jar, jbossws14-core.jar > > Time Spent: 7 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-21 13:41:18
[ http://jira.jboss.com/jira/browse/JBWS- 1860?page=comments#action_12388686 ] Prabhat Jha commented on JBWS-1860: ----------------------------------- WS sample tests pass 100% with java 5. With Java 1.4: There is a problem. On server side, the error is 2007-11-21 14:30:33,493 DEBUG [javax.xml.rpc.soap.SOAPFaultException] new SOAPFaultException [code={http://sche mas.xmlsoap.org/soap/envelope/}Client,string=java.lang.N ullPointerException,actor=null,detail=null] 2007-11-21 14:30:33,493 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception java.lang.NullPointerException at org.jboss.ws.core.utils.DOMUtils.getOwnerDocument(DOMUtils.j ava:529) at org.jboss.ws.core.soap.SOAPDocument.<init>(SOAPDocumen t.java:55) at org.jboss.ws.core.soap.SOAPPartImpl.<init>(SOAPPartImp l.java:77) at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMess ageImpl.java:66) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(Mess ageFactoryImpl.java:243) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(Mess ageFactoryImpl.java:179) at org.jboss.ws.core.server.ServiceEndpoint.processRequest(Serv iceEndpoint.java:197) at org.jboss.ws.core.server.ServiceEndpointManager.processReque st(ServiceEndpointManager.java:449) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPo st(AbstractServiceEndpointServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.jboss.ws.core.server.AbstractServiceEndpointServlet.serv ice(AbstractServiceEndpointServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Repl yHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFi lter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(App licationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(Standar dWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(Standar dContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invok e(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCo ntextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHo stValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepo rtValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(Ca chedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(Standard EngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAd apter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Proce ssor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11Connection Handler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(Poo lTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(Maste rSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:534) Magesh, can you verify that you are getting the same error on your end? Fixing this should fix tests run with jdk1.4. > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Prabhat Jha > Priority: Critical > Attachments: jbossws-client.jar, jbossws-core.jar, jbossws14-client.jar, jbossws14-core.jar > > Time Spent: 7 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-26 09:53:18
[ http://jira.jboss.com/jira/browse/JBWS- 1860?page=comments#action_12389105 ] Prabhat Jha commented on JBWS-1860: ----------------------------------- Any update on this Magesh? > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Magesh krishna 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-26 21:29:18
[ http://jira.jboss.com/jira/browse/JBWS- 1860?page=comments#action_12389227 ] Magesh krishna B commented on JBWS-1860: -------------------------------------- Missed your comment. Will check now. > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Magesh krishna 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Updated: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-27 00:00:18
[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh krishna 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 krishna 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 krishna B DATE: 16th November 2007 > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Magesh krishna 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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Updated: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-27 00:02:18
[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh krishna B updated JBWS-1860: --------------------------------- Attachment: (was: jbossws14-client.jar) > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Magesh krishna B > Priority: Critical > Attachments: jbossws-client.jar, jbossws-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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Updated: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-27 00:02:18
[ http://jira.jboss.com/jira/browse/JBWS-1860?page=all ] Magesh krishna B updated JBWS-1860: --------------------------------- Attachment: (was: jbossws14-core.jar) > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: Magesh krishna B > Priority: Critical > Attachments: jbossws-client.jar, jbossws-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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
United States	2007-11-27 00:04:18
[ http://jira.jboss.com/jira/browse/JBWS- 1860?page=comments#action_12389237 ] Magesh krishna B commented on JBWS-1860: -------------------------------------- Prabhat, My bad! This patch is only applicable for JDK1.5 as the API ThreadLocal.remove is not there in JDK1.4. So kindly release it only for JDK1.5. I have updated the patch instruction too here. > Memory leak fixes for JBossWS1.2.1 > ---------------------------------- > > Key: JBWS-1860 > URL: http://ji ra.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 krishna B > Assigned To: JBoss QA Lead > Priority: Critical > Attachments: jbossws-client.jar, jbossws-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.atl assian.com/software/jira _______________________________________________ jbossws-issues mailing list jbossws-issueslists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-issues

[1-10] [11-20] [21-22]

about | contact Other archives ( Real Estate discussion Medical topics )