Resending email...somehow this did not make it to the list. Can you please try this?
-- dims ---------- Forwarded message ---------- From: Davanum Srinivas <[EMAIL PROTECTED]> Date: May 4, 2007 11:25 AM Subject: Re: AbstractHTTPSender not releasing connection To: [email protected] Ok then try this tactic. Can you get hold of the OperationContext for each invocation? Typically you can use myServiceContext.getLastOperationContext() to get the last OperationContext. You will have to start caching them though by calling myServiceClient.setCachingOperationContext(true) or you can create the OperationContext by calling myServiceContext.createOperationContext as well. Either way after the invocation is done you can call the following snippet to cleanup the HttpMethod. myOperationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); _messageContext.getTransportOut().getSender().cleanup(_messageContext); thanks, dims On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
Dims, what do you mean by "calling the complete method"?. In this scenario I'm using simple ServiceClient(s) sharing the same conf. context and attached to custom callbacks (I'm reusing the same ServiceClients for thousands of asynchronous requests). For my knowledge (see the link below) the cleanup (on the ServiceClient) should be called only at the end which, as I said, is after receiving thousands of responses. Are you then suggesting me to share an OperationClient for all my requests and to free resources as soon as I receive the response? Thanks, Michele
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
