Hi David, Thanks very much for this.
When you say: "Try 1.4.1. It's much better than 1.4 with this particular memory leak.", I take it you mean it is partially fixed, but not entirely fixed in 1.4.1. Is that correct? Did your pool of stubs continue to work for you? My goal is to completely eliminate any mem leaks from our app. Thanks, Matt. 2008/9/23 David Rees <[EMAIL PROTECTED]>: > On Mon, Sep 22, 2008 at 6:39 PM, Matt Friedman <[EMAIL PROTECTED]> wrote: >> Hi, was this issue fixed or resolved? I am running our service in >> JProbe and we are having the identical memory leak issues as described >> in this email chain. After roughly 900 requests the garbage collector >> goes to 100% and out of memory occurs. >> >> Over half the heap is full with instances related to: >> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap.* >> which is tied to the Axis2 implementation. We don't use edu.emory.* at >> all. >> >> We are running Axis2 v1.4. We're going to try a more recent release or >> the svn nightly build. > > Try 1.4.1. It's much better than 1.4 with this particular memory leak. > If your access to the stub constructor isn't synchronized, you may > need to serialize access to stub constructors as well. > > -Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Matt Friedman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
