Sanjiva, Just to explain a bit :)
A leak is when the method is finished the memory cannot be GC'ed. "consuming the memory unnecessarily" means that during a method's execution, it's taking more than appropriate what is needed :) Example http://issues.apache.org/jira/browse/AXIS2-264 is not a leak. thanks, dims On 12/30/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > On Tue, 2005-12-27 at 14:26 +0600, Eran Chinthaka wrote: > > Hi all, > > > > Just wanted to give you an update on Axis2's performance in threading > > environment. > > > > I ran simple EchoRawXMLTest multiple times using threads. First I tried > > this with the SimpleHTTPServer and then I deployed the service in Tomcat > > and tested. > > When I ran the test with SimpleHTTPServer, there were severe thread > > problems, when the number of threads increases more than 12. But with > > Tomcat it could handle 600 threads without a problem. So I believe this > > threading problem is with the SimpleHTTPServer and not with some other > > Axis2 component. > > OK. > > > At the same time when I ran more than 600 threads, I got > > OutOfMemoryError, which now I'm looking in to. Seems like OM is > > consuming the memory unnecessarily. Please note that that this is not a > > memory leak. > > Hmmmmm. Let me see whether I can combine the last two statements and > make sense: (1) uses memory unnecessarily, and (2) not a memory leak. > Hmmmmm. You must be using a higher order kind of logic than what my > simple mind concludes: its a memory leak. ;-). > > Sanjiva. > > -- Davanum Srinivas : http://wso2.com/blogs/
