You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "vd (JIRA)" <ax...@ws.apache.org> on 2005/01/15 01:34:16 UTC
[jira] Created: (AXIS-1765) Memory leak when setting server's service as global scope
Memory leak when setting server's service as global scope
---------------------------------------------------------
Key: AXIS-1765
URL: http://issues.apache.org/jira/browse/AXIS-1765
Project: Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2RC2
Environment: MS windows xp, sp2
Reporter: vd
When setting the scope of my service to application, the client side will run out of memory after 5-10 thousand hits. The service object on the server side is thread safe and works with both application and request scope. The server does not have any leak.
To fix memory leak, inside the generated stub, I wrap the call with a try/catch/finally, and in that, I put:
_call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
This would clear out the memory and no more leak.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1765) Memory leak when setting server's service as global scope
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1765?page=comments#action_57905 ]
Davanum Srinivas commented on AXIS-1765:
----------------------------------------
2 questions...does it happen only for application scope? can you please upload the modified stub?
thanks,
dims
> Memory leak when setting server's service as global scope
> ---------------------------------------------------------
>
> Key: AXIS-1765
> URL: http://issues.apache.org/jira/browse/AXIS-1765
> Project: Axis
> Type: Bug
> Components: Basic Architecture
> Versions: 1.2RC2
> Environment: MS windows xp, sp2
> Reporter: vd
>
> When setting the scope of my service to application, the client side will run out of memory after 5-10 thousand hits. The service object on the server side is thread safe and works with both application and request scope. The server does not have any leak.
> To fix memory leak, inside the generated stub, I wrap the call with a try/catch/finally, and in that, I put:
> _call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
> This would clear out the memory and no more leak.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira