Dear Ron,
The reason that I set up the timeout is that one of my service takes a long
time, about 67 seconds. After setting the timeout, the client does not get
exceptions for the long invocation.
If I called the service in the following way, only the first two are
executed. The server did not crash at all. From the 3rd one, timeout
exceptions are generated. But the problem is solved if the line,
serviceClient.cleanupTransport is added after the invocation.
CategorizedHubClient.Print();
CategorizedHubClient.Print();
CategorizedHubClient.Print();
CategorizedHubClient.Print();
CategorizedHubClient.Print();
CategorizedHubClient.Print();
CategorizedHubClient.Print();
Thanks so much!
LB
On Wed, Mar 16, 2011 at 12:25 AM, Ron Wheeler <
rwhee...@artifact-software.com> wrote:
> Why did it timeout?
> What did you see in the logs.
> Did the service crash?
> How long did the client wait before timing out?
>
> As far as we have seen, you can call web services as fast as it can service
> the request.
>
> Ron
>
>
> On 15/03/2011 11:17 AM, Bing Li wrote:
>
> Dear all,
>
> Anyone could answer this question?
>
> Your help is highly appreciated!
>
> LB
>
> On Tue, Mar 15, 2011 at 4:22 AM, Bing Li <lbl...@gmail.com> wrote:
>
>> Dear all,
>>
>> I tried to call published Web services. It worked fine. However, when
>> invoking one service in more than two times continuously, the client got
>> timeout exceptions from the 3rd one. Each invocation should be done very
>> quickly. It should not wait for so long time. I guess there must be some
>> limits on the invocation frequency? How to enlarge it?
>>
>> Thanks so much!
>> LB
>>
>
>
>
