In client-side stub code, look for the call object and try:
Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();
-- Lyndon Tiu
That does it. The memory no longer go up. The way I do it is inside
the generated stub, I wrap the call with a try/catch/finally, and in
that, I put your code below. I am not sure if this is the best way of
doing it. However, I am just testing. I won't use this code though.
- Axis memory leak Vy Ho
- Re: Axis memory leak Lyndon Tiu
- Re: Axis memory leak Vy Ho
- Re: Axis memory leak WAJSBERG Julien RD-BIZZ
- Re: Axis memory leak Vy Ho
- Re: Axis memory leak Vy Ho
- Re: Axis memory leak Tim K. (Gmane)
- Re: Axis memory leak V D
- Re: Axis memory leak Lyndon Tiu
- Re: Axis memory leak Davanum Srinivas