axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Réf. : RE: Axis 1.1 Memory leaks
Date Wed, 25 Feb 2004 12:29:26 GMT


I see your message and this url. Is it possible to know what are the xml parsers
you have used to reduce objects in memory... We have the same problems with
Thanks for your answer,

> A year or so ago we ran into a problem like this, but it wasn't with
> Axis - it was Xerces. A change of parser massively reduced the number of
> objects being created and destroyed, and greatly improved performance
> (this parser wouldn't do you any good, we wrote it to specifically solve
> this problem and had complete control over the XML being parsed). You
> might want to try Axis with a different parser.

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

> Luciano

Les informations contenues dans ce message sont confidentielles et peuvent constituer des
informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit
de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous
avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes
ses copies, et d en avertir immediatement l expediteur par message de retour....
Il est impossible de garantir que les communications par messagerie electronique arrivent
en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur
n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter.
--- ----------------------------------------------------- ---
The information contained in this e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose or use any part of it. If
you have received this message in error, please delete it and all copies from your system
and notify the sender immediately by return e-mail.
E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender
does not accept liability for any errors or omissions which arise as a result.

View raw message