Hello,
as I said in my previous email, my guess is that the problem lies at
the transport level. In order to confirm (or deny) my assumption you can
1 - not reuse the same HttpClient between calls
2 - customize your HttpConnectionManager as I suggested you in my
previous email.
Michele
On 16 Feb 2008, at 14:52, Pär Malmqvist wrote:
Hi!
I have noticed that the combination below sometimes hangs on the
third call if the server response always is an AxisFault.
But I have not had time to track it down complete so it would be
interesting to here from you.
What happens when you send a call three times in a row and the
response is always an AxisFault with an error message?
I hope it is not that hard to find out what parameters to use in
your call to get an AxisFault from the server.
Thanks!
/Pär
> Date: Sat, 16 Feb 2008 03:30:16 -0800
> From: [EMAIL PROTECTED]
> To: [email protected]
> Subject: Re: Axis2 client hangs with multiple requests in one
session
>
>
> Thanks, Michele!
>
> The combination of these 2 lines works for multiple requests/
responses:
> options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, true);
> options.setCallTransportCleanup(true);
>
> This line only tracks the cookie "JSESSIONID" but nothing else:
> options.setManageSession(true);
> --
> View this message in context: http://www.nabble.com/Axis2-client-
hangs-with-multiple-requests-in-one-session-tp15514156p15517229.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Express yourself instantly with MSN Messenger! MSN Messenger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
