axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimuthu Gamage" <>
Subject Re: Axis2/C Memory Leaks
Date Tue, 20 Nov 2007 07:06:44 GMT
You dont need to free any axis2, adb related thing in your server side when
you works on generated code using wsdl2c (at least Theoretically:) ) . Only
thing you need to do is write the business logic, and free whatever you
malloced inside there.


On Nov 20, 2007 3:34 AM, <> wrote:

> Hi,
> I am designing some web service client code using the Axis2/C framework
> (used WSDL2C to generate client stubs that call the framework).  I have
> a separate executable C file (C file that a main()) that calls the stub.
> When I ran valgrind initially on it, I saw many memory leaks from this;
> 49 loss records to be exact.  However, after inserting axis2_stub_free
> and axutil_env_free before my end return statement in my executable C
> file, I noticed that the loss records decreased greatly to 5.  I noticed
> that this freeing of the stub and env variables is not in the sample
> client code.  Should the sample client code also demonstrate this
> freeing, and is this freeing logical to do on the client side?  Also, I
> did some initial tests on the server side and noticed many memory leaks
> as well.  Should this client-side freeing be also implemented on my
> server code, or is the server-side freeing done differently and how if
> anyone can describe where to insert the freeing statements?

> Thanks,
> Edward
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message