Alex Bolgarov wrote:
Samisa, thank you; I checked out the SVN trunk version, build it and
run the test again.
On the server side (mod_axis2) there is no more memory leaks: I run
the test with 10 iterations, it took 4 minutes, httpd process
memory usage is stable and is not increasing.
But n
Hi,
Other solution may be we could define AXIS2_LIBXML2_DEFINED with
--enable-libxml2 and modify the logic according to it. There are only 4 or 5
places that need to be changed.
+1 for fixing this before 1.3.1 release.
thanks,
Dinesh
On Wed, Apr 16, 2008 at 11:58 AM, Milinda Pathirage <
[
Hi,
I think the hack samisa proposed earlier is not working, because we didn't
include any header files specific to guththila inside axiom code which
related to om_stax_builder.c. If we include it in axiom_xml_reader.h, it
worked well. But this hack is not acceptable due to it parser specific code
Milinda Pathirage wrote:
Hi Alex and Samisa,
This bug was caused by recent change of default parser. In the
om_stax_builder.c, we previously check whether guththila is enabled
and free the comment vlaue when we encounter a comment. Now guththila
is default we don have AXIS2_GUTHTHILA_ENABLED
Alex,
In the mean time, try with libxml2 paarser.
Samisa...
Samisa Abeysinghe wrote:
Samisa Abeysinghe wrote:
Alex Bolgarov wrote:
On Wed, Apr 9, 2008 at 3:36 PM, Samisa Abeysinghe <[EMAIL PROTECTED]>
wrote:
In the mean time, please send the valgrind log.
I did send the valgrind
Samisa Abeysinghe wrote:
Alex Bolgarov wrote:
On Wed, Apr 9, 2008 at 3:36 PM, Samisa Abeysinghe <[EMAIL PROTECTED]>
wrote:
In the mean time, please send the valgrind log.
I did send the valgrind log to the list
Sorry, I missed it (was a bit sleepy at the time I replied ;) )
Lookin
Alex Bolgarov wrote:
On Wed, Apr 9, 2008 at 3:36 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
In the mean time, please send the valgrind log.
I did send the valgrind log to the list
Sorry, I missed it (was a bit sleepy at the time I replied ;) )
Looking at the log, it is a new
On Wed, Apr 9, 2008 at 3:36 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> In the mean time, please send the valgrind log.
I did send the valgrind log to the list :) - you can even see it in
the marc.info archive, at the bottom of the message:
http://marc.info/?l=axis-c-user&m=120776918704827
Alex Bolgarov wrote:
Samisa, thank you; I checked out the SVN trunk version, build it and
run the test again.
On the server side (mod_axis2) there is no more memory leaks: I run
the test with 10 iterations, it took 4 minutes, httpd process
memory usage is stable and is not increasing.
But n
Samisa, thank you; I checked out the SVN trunk version, build it and
run the test again.
On the server side (mod_axis2) there is no more memory leaks: I run
the test with 10 iterations, it took 4 minutes, httpd process
memory usage is stable and is not increasing.
But now there is a memory le
Local pools have been integrated to mod_axis2 in Axis2/C trunk.
You may run the tests again and see the improved memory footprint.
Samisa...
Samisa Abeysinghe wrote:
Alex Bolgarov wrote:
On Mon, Mar 31, 2008 at 11:17 PM, Uthaiyashankar <[EMAIL PROTECTED]>
wrote:
I doubt whether it is a me
Alex Bolgarov wrote:
On Mon, Mar 31, 2008 at 11:17 PM, Uthaiyashankar <[EMAIL PROTECTED]> wrote:
I doubt whether it is a memory leak. When using mod_axis2, memory
management is done by apache apr. Memory is released only when pools are
destroyed. Memory will not be released when calling AX
But If you are going to use this on a production environment it is
better to use apr_pools. Because malloc() allocates memory from OS but
with apr_pools it is from the pool. so as performance wise it is better.
-Manjula.
On Tue, 2008-04-01 at 20:10 -0800, Supun Kamburugamuva wrote:
> Hi Alex,
>
Hi Alex,
Since we don't have memory leaks with simple http server, using
malloc()/free() will solve your problem.
Regards,
Supun..
On Tue, Apr 1, 2008 at 6:15 AM, Alex Bolgarov <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 31, 2008 at 11:17 PM, Uthaiyashankar <[EMAIL PROTECTED]> wrote:
> >
> > I d
On Mon, Mar 31, 2008 at 11:17 PM, Uthaiyashankar <[EMAIL PROTECTED]> wrote:
>
> I doubt whether it is a memory leak. When using mod_axis2, memory
> management is done by apache apr. Memory is released only when pools are
> destroyed. Memory will not be released when calling AXIS2_FREE.
> (axis2
No, MaxRequstsPerClient is set to 0, and yes, I understand that I can
use this to kill old children processes with accumulated memory leaks
and start new fresh ones, but you know, using MaxRequestPerClient is
kind of cheating :) - there should not be memory leaks in the
mod_axis2 in the first p
Alex Bolgarov wrote:
On Sat, Mar 29, 2008 at 10:48 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
Alex Bolgarov wrote:
> Hi again.
>
> I've just run the echo service sample within the Apache2 httpd server
> (with the mod_axis2 module), I used the echo client but put the
> send-receive
On Sat, Mar 29, 2008 at 10:48 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> Alex Bolgarov wrote:
> > Hi again.
> >
> > I've just run the echo service sample within the Apache2 httpd server
> > (with the mod_axis2 module), I used the echo client but put the
> > send-receive into the loop w
Alex Bolgarov wrote:
Hi again.
I've just run the echo service sample within the Apache2 httpd server
(with the mod_axis2 module), I used the echo client but put the
send-receive into the loop with 1,000,000 iterations.
What I observed, was constant increasing of the memory (both resident
and vi
Hi again.
I've just run the echo service sample within the Apache2 httpd server
(with the mod_axis2 module), I used the echo client but put the
send-receive into the loop with 1,000,000 iterations.
What I observed, was constant increasing of the memory (both resident
and virtual, as the 'top' com
20 matches
Mail list logo
