Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67FF1.8889D0D9"
Subject: Axis2 High memory usage, OutOfMemory exception
Date: Thu, 25 May 2006 07:51:18 -0400
Message-ID: <32EF7BBBB7373846BAA10F8818A8B50C2467CD@scpmail1.NTSCD.C-COR.com>
Thread-Topic: Axis2 High memory usage, OutOfMemory exception
Thread-Index: AcZ/8Yev7bFDKBRCRACFf/02NmT06w==
From: "Ramanathan, Subramanyam" <sramanathan@c-cor.com>
To: "Axis-User \(E-mail\)" <axis-user@ws.apache.org>

------_=_NextPart_001_01C67FF1.8889D0D9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,=20

I have been trying out Axis 2.0 over the past week, with the =
configuration :
Axis2 version 1.0
Tomcat 5.5.17
jdk 1.5.0_04

I have tried using the sample "Axis2SampleDocLitService" that has been =
given. I generated the stubs and skeletons using the wsdl provided with =
the axis2 distribution (samples/wsdl/Axis2SampleDocLit.wsdl) ,  as shown =
in the user guide, using the xmlbeans option for data binding.

I have a http client which I use to post the xml request to the server, =
and I got proper responses when I tested it with the client.

However, I have noticed that when I pump requests at a rapid rate, the =
memory usage keeps on increasing rapidly (checked using jmx console), in =
some cases ultimately leading to a jvm crash with an OutOfMemory =
Exception.  This was occurring when default mx(which is 64M) was used.

I also tried setting the JVM mx option to 128M (-Xmx128M)  and ran the =
test again. However, the memory usage keeps increasing all the way till =
it reaches 128 Mb, too, where it again crashes if I continue pumping =
further.=20
If I stop pumping requests at around that time, and wait for around half =
an hour, I notice that the memory usage begins to reduce, and slowly =
come back to the original value (10M approx.)  upon forcing a GC.=20

I have also deployed axis1 on the same tomcat installation, with the =
intention of comparing performance. When I try the same test there, ie, =
pumping requests, I don't find any alarming memory increase.

Why is so much memory being used, and why does it grow to fill however =
much memory is available ? Is it a memory leak, or is there any way I =
can limit the amount of memory being used ? The memory usage does come =
down, but it takes a very long time for this. This would surely affect =
the performance of any webservice I try to deploy with axis2, and it may =
even result in the service being unavailable because of a crash.

Could you please help me out ?

Regards,=20
Subramanyam

------_=_NextPart_001_01C67FF1.8889D0D9
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.5">
<TITLE>Axis2 High memory usage, OutOfMemory exception</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi, </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have been trying out Axis 2.0 over =
the past week, with the configuration :</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Axis2 version 1.0</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Tomcat 5.5.17</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">jdk 1.5.0_04</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have tried using the sample =
&quot;Axis2SampleDocLitService&quot; that has been given. I generated =
the stubs and skeletons using the wsdl provided with the axis2 =
distribution (samples/wsdl/Axis2SampleDocLit.wsdl) ,&nbsp; as shown in =
the user guide, using the xmlbeans option for data binding.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have a http client which I use to =
post the xml request to the server, and I got proper responses when I =
tested it with the client.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">However, I have noticed that when I =
pump requests at a rapid rate, the memory usage keeps on increasing =
rapidly (checked using jmx console), in some cases ultimately leading to =
a jvm crash with an OutOfMemory Exception.&nbsp; This was occurring when =
default mx(which is 64M) was used.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I also tried setting the JVM mx option =
to 128M (-Xmx128M)&nbsp; and ran the test again. However, the memory =
usage keeps increasing all the way till it reaches 128 Mb, too, where it =
again crashes if I continue pumping further. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">If I stop pumping requests at around =
that time, and wait for around half an hour, I notice that the memory =
usage begins to reduce, and slowly come back to the original value (10M =
approx.)&nbsp; upon forcing a GC. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have also deployed axis1 on the same =
tomcat installation, with the intention of comparing performance. When I =
try the same test there, ie, pumping requests, I don't find any alarming =
memory increase.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Why is so much memory being used, and =
why does it grow to fill however much memory is available ? Is it a =
memory leak, or is there any way I can limit the amount of memory being =
used ? The memory usage does come down, but it takes a very long time =
for this. This would surely affect the performance of any webservice I =
try to deploy with axis2, and it may even result in the service being =
unavailable because of a crash.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Could you please help me out ?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Subramanyam</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C67FF1.8889D0D9--