axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rees" <dree...@gmail.com>
Subject Re: When do cleanup functions need to be called?
Date Wed, 30 Jul 2008 02:50:13 GMT
On Tue, Jul 29, 2008 at 5:51 PM, David Rees <drees76@gmail.com> 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 service can process requests for over an hour where it
> would die within minutes).

Unfortunately, I was mistaken. Calling cleanup() doesn't appear to
help at all, unfortunately I also switched to Axis2 1.4.1 RC1 at the
same time which appears to to have reduced the rate at which the heap
bloats, but eventually, it still suffers the same fate.

However, eventually, the service (running under Tomcat 5.5.26) still
runs out of heap space with the same symptoms - hundreds of thousands
of ConcurrentHashMap objects. These all appear to trace back to the
AxisServlet through this chain:

AxisBindingOperation -> AxisBindingMessage ->ConcurrentHashMap ->
AxisBinding -> AxisBindingOperation -> AxisEndpoint -> HashMap ->
AxisService -> OutInAxisOperation -> HashMap -> AxisConfiguration ->
AxisServlet.

So what's going on here? I can't imagine that I'm the only one making
Axis2 client calls from a Axis2 web service and running into this
issue - either I'm doing something unique or I'm doing something
wrong...

Thanks

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Mime
View raw message