[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1860) Memory leak fixes for JBossWS1.2.1
Prabhat Jha (JIRA)
jira-events at lists.jboss.org
Wed Nov 21 14:41:18 EST 2007
[ 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://schemas.xmlsoap.org/soap/envelope/}Client,string=java.lang.NullPointerException,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.java:529)
at org.jboss.ws.core.soap.SOAPDocument.<init>(SOAPDocument.java:55)
at org.jboss.ws.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:77)
at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:66)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:243)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:179)
at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:197)
at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:449)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.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://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: 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.atlassian.com/software/jira
More information about the jbossws-issues
mailing list