You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by David Illsley <da...@gmail.com> on 2007/03/14 17:05:04 UTC
Fwd: [axis2] out of memory error
Thanks Michele.
Does anyone see a problem with this? I think it's ok but wanted to
check it doesn't break anyone's non-standard MEPs or WS-RM replayed
messages or something unusual like that?
David
---------- Forwarded message ----------
From: Michele Mazzucco <Mi...@ncl.ac.uk>
Date: 14-Mar-2007 15:54
Subject: Re: [axis2] out of memory error
To: axis-user@ws.apache.org
David,
I did it for you :). You were right, no elements are removed from the
HashMap in org.apache.axis2.util.CallbackReceiver.
In method receive(), replacing callbackStore.get(messageID) with
callbackStore.remove(messageID) will fix the problem.
Michele
On 13 Mar 2007, at 22:54, David Illsley wrote:
> If it's the client, and there's a single CallbackReceiver, I've been
> suspicious about the code in there which never removes anything from
> it's callbackStore HashMap. I haven't had a chance to look into this
> in detail though.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Fwd: [axis2] out of memory error
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
+1 from me...
Nicholas Gallardo
WebSphere - WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016
"David Illsley" <da...@gmail.com>
03/14/2007 11:05 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org, Michele.Mazzucco@ncl.ac.uk
cc
Subject
Fwd: [axis2] out of memory error
Thanks Michele.
Does anyone see a problem with this? I think it's ok but wanted to
check it doesn't break anyone's non-standard MEPs or WS-RM replayed
messages or something unusual like that?
David
---------- Forwarded message ----------
From: Michele Mazzucco <Mi...@ncl.ac.uk>
Date: 14-Mar-2007 15:54
Subject: Re: [axis2] out of memory error
To: axis-user@ws.apache.org
David,
I did it for you :). You were right, no elements are removed from the
HashMap in org.apache.axis2.util.CallbackReceiver.
In method receive(), replacing callbackStore.get(messageID) with
callbackStore.remove(messageID) will fix the problem.
Michele
On 13 Mar 2007, at 22:54, David Illsley wrote:
> If it's the client, and there's a single CallbackReceiver, I've been
> suspicious about the code in there which never removes anything from
> it's callbackStore HashMap. I haven't had a chance to look into this
> in detail though.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org