]
To: axis-user@ws.apache.org
Sent: Tuesday, March 6, 2007 6:32:42 PM
Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching
You can cache configContext itself!
-- dims
On 3/6/07, sean curtis [EMAIL PROTECTED] wrote:
When running some recent tests against our webserver that contains our
as a client reads this and gets the benefit of OOM
better performance and elminating a pervasive memory leak problem.
- Original Message
From: Davanum Srinivas [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, March 6, 2007 6:32:42 PM
Subject: Re: Axis2 Client performance
seeing the same
issues, with degraded performance and seeming to leak memory?
- Original Message
From: Michele Mazzucco [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, March 7, 2007 9:45:09 AM
Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching
Sean,
how
: Tuesday, March 6, 2007 6:32:42 PM
Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching
You can cache configContext itself!
-- dims
On 3/6/07, sean curtis [EMAIL PROTECTED] wrote:
When running some recent tests against our webserver that contains our
client code, it seems
Curtis,
I faced the same problem. It also leaks around 250KB per call. Though I
couldn't figure out the root set that is holding references to a lot
of OMElementImpl and OMTextImpl objects. The JVM was also crashing
every few days. Change the code generated to cache the
ConfigurationContext and
