Hi all;
I agree with Eran , that we keep complete context hierarchy in memory , we
have to address this issue , my idea is to have time out for each context
level and remove them from memory after the time complete.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Eran Chinthaka" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, December 08, 2005 10:18 AM
Subject: Re:[Axis2] Axis2+Tomcat(Windows): java.lang.OutOfMemoryError!?
Excellent test and amazing results !! I wish if I could be there too.
Anyway Gonçalo,
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
[EMAIL PROTECTED] 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 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 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 crashing
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çalo
