Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 3971 invoked from network); 8 Dec 2005 04:35:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Dec 2005 04:35:25 -0000 Received: (qmail 42511 invoked by uid 500); 8 Dec 2005 04:35:21 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 42479 invoked by uid 500); 8 Dec 2005 04:35:20 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 42468 invoked by uid 99); 8 Dec 2005 04:35:20 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 20:35:20 -0800 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=HTML_MESSAGE,PLING_QUERY,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ajith.ranabahu@gmail.com designates 64.233.184.195 as permitted sender) Received: from [64.233.184.195] (HELO wproxy.gmail.com) (64.233.184.195) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2005 20:35:20 -0800 Received: by wproxy.gmail.com with SMTP id i6so842800wra for ; Wed, 07 Dec 2005 20:34:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=klv2Hc/TxHl5BUQaBOjgJA67Mp+jeUhnYzQfpx8KXqR+FSV3WWJ8oye4IAiNVUE9gVLG4S7cTKgZPqmtDjjKCEW8h+tx1ESbzrImEIzw3+zZvmf5v77LbIcTfuOeOF6WMLXKltddg+ZA5QBF2AzBSAOyTZix8Tdv2F8L/U+xRcA= Received: by 10.65.112.20 with SMTP id p20mr2552669qbm; Wed, 07 Dec 2005 20:34:59 -0800 (PST) Received: by 10.64.148.5 with HTTP; Wed, 7 Dec 2005 20:34:59 -0800 (PST) Message-ID: Date: Thu, 8 Dec 2005 10:34:59 +0600 From: Ajith Ranabahu To: axis-dev@ws.apache.org, chinthaka@opensource.lk Subject: Re: [Axis2] Axis2+Tomcat(Windows): java.lang.OutOfMemoryError!? In-Reply-To: <4397B408.60800@opensource.lk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22017_5563871.1134016499301" References: <1133986473.439742a99c88c@mail.dei.uc.pt> <4397B408.60800@opensource.lk> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_22017_5563871.1134016499301 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yep, An excellent test which we could not have done in our own environment. Since you have the setup already, here's a little "request" (:))from us to pinpoint the problem. Eran has a valid point about the heap size. You should definitely try it an= d see. But I've a hunch that this could be a problem with Axis2. So would you be able to run a profiler and check which object instances produce this problem ? I guess you can use one of the open source profilers like ejp ( http://ejp.sourceforge.net/) or Jprofiler has an evaluation version that should work for this case. On 12/8/05, Eran Chinthaka wrote: > > Excellent test and amazing results !! I wish if I could be there too. > > Anyway Gon=E7alo, > > I admit that we haven't done good profiling on Axis2. For some reason it > is getting postponed. But its not a good excuse. > > Since you have some good configuration, can you help us to improve ? We > all really appreciate if you can help in that. If you have time, please > find the bottle necks and post them here. Lets discuss and fix them. > I know for sure there is a problem in life cycles of context hierarchy. > > Another small issue. Did you try increasing the heap memory of Tomcat. > However much memory you have, if the heap size is small, you are not > gaining (I think) from your huge memory. > > -- Chinthaka > > gjesus@student.dei.uc.pt wrote: > > >Hi, > > > >Sorry to bother you guys again, but i'm having another problem! I dont' > know > >what it's happening but my webservice in Java through Axis2 (with > Tomcat5.5) it > >can only process about 4880 requests in less that one minute, then it > stops and > >starts to throw java.lang.OutOfMemoryError Exceptions! > >Note that this webservice is almost identical to another one that was > running > >through Axis(1.3) that didn't give me any problem in the exactly same > >conditions. > > > >The Server(Tomcat) and WebService are running in a Windows Server 2003 i= n > a AMD > >Dual Opteron (2x2GHZ) with 2GB DDR Dual Channel (actually it's 4GB but w= e > >removed 2GB for these tests). > > > >I'm running a Benchmark Test in a cluster! The Server is receiving > requests from > >10 machines, each of them has 10 connections sending requests in burst > mode > >(send-receive-send...). It's a stress test with the objective of crashin= g > the > >server...but i hoped that would last longer than 1 minute (!?). > > > >If you have a solution it will be great, but knowing the reason (i > presume it's > >not due to my java service application...) for this to happen will also > be well > >received! > > > >Thanks, > >Gon=E7alo > > > > > > > -- Ajith Ranabahu ------=_Part_22017_5563871.1134016499301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yep, An excellent test which we could not have done in our own environment. Since you have the setup already, here's a little "request" (:))from us to pinpoint the problem.

Eran has a valid point about the heap size. You should definitely try it and see. But I've a hunch that this could be a problem with Axis2. So would you be able to run a profiler and check which object instances produce this problem ? I guess you can use one of the open source profilers like  ejp (http://ej= p.sourceforge.net/) or Jprofiler has an evaluation version that should work for this case.

On 12/8/05, Eran Chinthaka= <chinthaka@opensource.lk= > wrote:
Excellent test and amazing results !!  I wish if I could be ther= e too.

Anyway Gon=E7alo,

I admit that we haven't done good profiling on= Axis2. For some reason it
is getting postponed. But its not a good excu= se.

Since you have some good configuration, can you help us to impro= ve ? We
all really appreciate if you can help in that. If you have time, please=
find the bottle necks and post them here. Lets discuss and fix them.I know for sure there is a problem in life cycles of context hierarchy.

Another small issue. Did you try increasing the heap memory of Tomc= at.
However much memory you have, if the heap size is small, you are not=
gaining (I think) from your huge memory.

-- Chinthaka

gjesus@student.dei.uc.pt wr= ote:

>Hi,
>
>Sorry to bother you guys again, but i'm = having another problem! I dont' know
>what it's happening but my webs= ervice in Java through Axis2 (with=20 Tomcat5.5) it
>can only process about 4880 requests in less that one = minute, then it stops and
>starts to throw java.lang.OutOfMemoryError= Exceptions!
>Note that this webservice is almost identical to anothe= r one that was running
>through Axis(1.3) that didn't give me any problem in the exactly sa= me
>conditions.
>
>The Server(Tomcat) and WebService are = running in a Windows Server 2003 in a AMD
>Dual Opteron (2x2GHZ) with= 2GB DDR Dual Channel (actually it's 4GB but we
>removed 2GB for these tests).
>
>I'm running a Benchmar= k Test in a cluster! The Server is receiving requests from
>10 machin= es, each of them has 10 connections sending requests in burst mode
>(= send-receive-send...). It's a stress test with the objective of crashing th= e
>server...but i hoped that would last longer than 1 minute (!?).
= >
>If you have a solution it will be great, but knowing the reason= (i presume it's
>not due to my java service application...) for this= to happen will also be well
>received!
>
>Thanks,
>Gon=E7alo
>
>>



--
Ajith Ranabah= u ------=_Part_22017_5563871.1134016499301--