Title: RE: Axis 1.1 Memory leaks

Hi Nelson,
the problem that I'm experiencing is related to some (known?) Axis problem to
handle large xml documents.
In fact, I'm sending back and forth binary files or large xml files (2.5Mb) without using the SAAJ specification or the code used in the /sample/attachemnt folder of Axis1.1 distrib.

I have simply designed an interface that uses complex objects to transport data (i.e. array of DataHandler). Than
I generate the wsdl and the wsdd and deploy.
Everything works fine until I start using large documents.
The annoyng thing is that the Attachment sample works perfectly even with 100Mb documents without having to tune the memory heap. This is because in that code they use attachments outside the Soap Envelope body. Also, the sample code on the server side is completely "custom".

My goal was to define a simple build process and use the proxy classes generated by wsdl2java, without having to write a lot of hard-to-maintain code.

By the way, I have also tried with version 1.2beta and I have the same results.

Luciano

-----Original Message-----
From: Nelson Minar [mailto:[EMAIL PROTECTED]]
Sent: Monday 23 February 2004 17:39
To: [EMAIL PROTECTED]
Subject: Re: Axis 1.1 Memory leaks


>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 :-)

 

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.

Reply via email to