axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Axis 1.1 Memory leaks
Date Mon, 23 Feb 2004 17:07:01 GMT
Hi Ian,
increasing the heap size is a risky solution in my opinion, because (at least in my case)
I will never know when the memory will be enough to handle my large xml document.
I believe that there is some inefficiency in Axis code when it comes to handle
large xml documents. In the next days I will perform some JProbe checking to see
which component is eating all the memory.

Check out this thread:


-----Original Message-----
From: []
Sent: Monday 23 February 2004 17:50
Subject: Re: Axis 1.1 Memory leaks

FWIW, we run with an initial heap size of 256MB and a max heap size of
512MB, and that seems to work pretty welll...


                    Nelson Minar                                                         
                    <nelson@monkey       To:              
                    .org>                cc:                                          
                                         Subject:     Re: Axis 1.1 Memory leaks          
                    11:38 AM                                                             
                    Please respond                                                       
                    to axis-user                                                         

>Last week we did some heavy testing on the web service and we
>discovered that we cannot send documents bigger than 1.5Mb. Axis
>fails with a OutOfMemory exception.

How are you encoding the file you're sending? Is it some sort of SOAP
attachment, or is it an element in the query?

Your most direct fix is to increase JVM memory, as you found via the
-Xmx flag. 32 megs is just not a lot of heap.

I've noticed Axis is not terribly memory efficient - using 20 megs of
RAM to handle 1 meg of data seems about typical. Things got a lot
better when I configured Axis to not send xsi:type data when
generating messages. I don't know if that made Axis in general more
efficient, or it was just the fact that the XML is smaller.

The title of your message is "memory leaks", but your experience is
really about memory inefficiency. Do you also have evidence of an
actual memory leak, something where memory is not returned after the
call is over?

PS - I've noticed that axis-user has about 95% questions and 5%
answers. That's too bad! I'm going to try answering questions I know
the answers to, maybe others can as well? I bet there's a market for
Axis consultants out there :-)

This transmission may contain information that is privileged, confidential and/or exempt from
disclosure under applicable law. If you are not the intended recipient, you are hereby notified
that any disclosure, copying, distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error,
please immediately contact the sender and destroy the material in its entirety, whether in
electronic or hard copy format. Thank you.

Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither
be binding nor construed as constituting a commitment by the ECB except where provided for
in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised
disclosure, use or dissemination, either in whole or in part, is prohibited.
If you have received this e-mail in error, please notify the sender immediately via e-mail
and delete this e-mail from your system.

View raw message