that the title of the existing post (Re:
When do cleanup functions need to be called?), didn't represent what
this thread is actually about.
I was afraid the importance of the thread might be missed, as the old
title no longer applies.
Hopefully, this isn't inappropriate. Sorry if I've annoyed anyone
Amila Suriarachchi wrote:
Please try with a Nighly build. As I think this could be the problem.
...
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Any idea when an release with this fix is planned ? Would this be in 1.4.2
?
--
View this message in
Please try with a Nighly build. As I think this could be the problem.
in Stub class we have this at the clean up method.
protected void finalize() throws Throwable {
super.finalize();
cleanup();
}
public void cleanup() throws AxisFault {
I have the same problem as described here.
Upgrading to 1.4.1 has reduced the leak.
I am now going to try the pool of stubs as well for the remaining.
Dave, is your client running in Tomcat ?
My problem only occurs when I am accessing the WS using a stub from within
the same tomcat
On Mon, Oct 6, 2008 at 5:27 PM, Mel T [EMAIL PROTECTED] wrote:
I have the same problem as described here.
Upgrading to 1.4.1 has reduced the leak.
I am now going to try the pool of stubs as well for the remaining.
Dave, is your client running in Tomcat ?
My problem only occurs when I am
I have the same problem as described here.
Upgrading to 1.4.1 has reduced the leak.
I am now going to try the pool of stubs as well for the remaining.
Dave, is your client running in Tomcat ?
My problem only occurs when I am accessing the WS using a stub from
within
the same tomcat
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
Hi,
I'm sorry for the re-post, but I was discussing this thread with a
co-worker and we postulated that the title of the existing post (Re:
When do cleanup functions need to be called?), didn't represent what
this thread is actually about.
I was afraid the importance of the thread might
do cleanup functions need to be called?), didn't represent what
this thread is actually about.
I was afraid the importance of the thread might be missed, as the old
title no longer applies.
Hopefully, this isn't inappropriate. Sorry if I've annoyed anyone.
So, renamed more appropriately, here
On Tue, Sep 23, 2008 at 5:16 AM, Matt Friedman [EMAIL PROTECTED] wrote:
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
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
On Tue, Jul 29, 2008 at 10:52 PM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
this method should be call when the MyServiceStub (see finalize method in
ServiceClient) is garbage collected. I am not sure why it is not being
called automatically.
I don't think that it's being garbage collected
On spec, wouldn't it be related to the scope of your services ?
http://www.developer.com/java/web/article.php/3620661
David Rees a crit:
On Tue, Jul 29, 2008 at 10:52 PM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
this method should be call when the MyServiceStub (see finalize
On Wed, Jul 30, 2008 at 2:15 PM, David Rees [EMAIL PROTECTED] wrote:
On Tue, Jul 29, 2008 at 10:52 PM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
this method should be call when the MyServiceStub (see finalize method in
ServiceClient) is garbage collected. I am not sure why it is not being
On Wed, Jul 30, 2008 at 4:22 AM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 2:15 PM, David Rees [EMAIL PROTECTED] wrote:
well see this code,
public static void clientCall1() {
MyServiceStub stub = new MyServiceStub(http://example.com/myservice;);
ClientCall1 req =
On Wed, Jul 30, 2008 at 2:09 AM, Pierre Muller [EMAIL PROTECTED] wrote:
On spec, wouldn't it be related to the scope of your services ?
http://www.developer.com/java/web/article.php/3620661
I don't think so - The default scope (request) should be fine. I don't
care about anything longer than
On Wed, Jul 30, 2008 at 11:08 PM, David Rees [EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 4:22 AM, Amila Suriarachchi
[EMAIL PROTECTED] wrote:
On Wed, Jul 30, 2008 at 2:15 PM, David Rees [EMAIL PROTECTED] wrote:
well see this code,
public static void clientCall1() {
On Tue, Jul 29, 2008 at 5:51 PM, David Rees [EMAIL PROTECTED] wrote:
After pulling my hair out for the past 24 hours trying to figure out
the root cause and desperately googling for answers, I finally found
that calling MyStub._getService().cleanup() appears to fix the leak
(at least the
On Wed, Jul 30, 2008 at 6:21 AM, David Rees [EMAIL PROTECTED] wrote:
I'm developing an application using Axis2 1.4 which consists of a
client and service. Stubs are generated using the wsdl2java tool using
ADB.
I am seeing what appears to be a huge resource leak when using the
client code
19 matches
Mail list logo
