I did some further code research and in my opinion it's absolutely legal to
reuse configurationcontext objects because by default the server's
ListenerManager.defaultConfigurationContext object will be used too.
so this brings me to the point, that using 'non-anonymous'-services (build
dynamically
Hi Gerhard,
Do you invoke the
org.apache.axis2.client.Stub.cleanup()
method after having finished with the stub??
This method removes the stub from its service-context.
This thread might be relevant.
http://marc.info/?l=axis-user&m=122213400714608&w=2
(DISCLAIMER: I have no internal knowledge
reuse them
On Tue, Jun 22, 2010 at 4:51 PM, gerhard presser wrote:
>
> I don't have any problems concerning the http-connnections!
> what's the recommended way for using configurationcontext-objects?
> 1) use them once per request
> 2) reuse them
>
> regards
>
>
> rahulYadav wrote:
> >
> > try se
I don't have any problems concerning the http-connnections!
what's the recommended way for using configurationcontext-objects?
1) use them once per request
2) reuse them
regards
rahulYadav wrote:
>
> try setting this...
>
>
> configurationContext.setProperty(Packages.org.apache.axis2.transpo
try setting this...
configurationContext.setProperty(Packages.org.apache.axis2.transport.http.HTTPConstants.REUSE_HTTP_CLIENT,
true);
gerpres wrote:
>
> FYI: I'm using axis 1.5.1
>
> I cannot confirm the problem mentioned at:
> http://old.nabble.com/Resuse-of-configurationcontext-ends-in-o
FYI: I'm using axis 1.5.1
I cannot confirm the problem mentioned at:
http://old.nabble.com/Resuse-of-configurationcontext-ends-in-out-of-memory-error-td26442083.html
Reusing ConfigurationContext - Memory leak
gerpres wrote:
>
> hi all,
> can a configurationcontext object been reused safely?
