Hello Kevin,
I fully understand the 'toughness' of the situation. Therefore I provide you
with more information.
1. De problem is definitely client side. The server immediately picks up on
the restarted client application. Also sometimes a part of our client
software is capable of communicating with the server. Also requests from the
client do not arrive at the server at all.
2. Meanwhile I tried tearing down and rebuilding the reference to the
WebService as soon as this problem occurs. Currently the client opens a
single proxy class reference for all requests. Do you know of best practises
in this?
Kind regards,
[quoted text, click to view] "Kevin Yu [MSFT]" wrote:
> Hi,
>
> This problem might be complex. It can be caused by many resons. The most
> probable reason, is because the internet traffic. It might be on either the
> server side or the client side. Also, there might be too many people
> accessing that web service, and make the server unable to respond in time.
>
> It's hard to say which one is the cause, you have to do more research on
> it. HTH.
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
Hi,
1. This can also be the network issue. Because the network can go bad in
different period. When certain client goes wrong, it might be the network
problem. When it restarts, the network is good again. So, I still can't
decide the cause of the problem.
2. The best practice for creating the proxy class is to use VS.NET IDE's
Add Web Reference, and let it generate the proxy class for you. As far as I
know, it generates a proxy class for each .asmx file.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Hello Kevin,
1. Is there possibly anti-DoS or fair-use logic in firewall and security
software of Windows XP?
2. My question on best practise is how to treat this proxy class. Must I
create an object ref for every transaction to the server or can I pool it or
can I keep a persistent object ref?
Kind regards,
Robbert
--
rvangeldrop
[quoted text, click to view] "Kevin Yu [MSFT]" wrote:
> Hi,
>
> 1. This can also be the network issue. Because the network can go bad in
> different period. When certain client goes wrong, it might be the network
> problem. When it restarts, the network is good again. So, I still can't
> decide the cause of the problem.
>
> 2. The best practice for creating the proxy class is to use VS.NET IDE's
> Add Web Reference, and let it generate the proxy class for you. As far as I
> know, it generates a proxy class for each .asmx file.
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
Hi Robbert,
1. Yes, this might be the firewall issue. But I can't be sure.
2. The the proxy object is actually a connection to the web service.
Whether to pool it depends on your app. Generally, I suggest you use a new
object to release the resources, if it is not called again and again. HTH.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Hello Kevin,
I now changed our code that it will tear down the webservice object
reference and create a new one as soon as succesive time-outs occur. The
frequency of persistent time-outs decreased but some clients still have them.
So far this is acceptable, but the issue is not solved. Please keep me
up-to-date if similar issues are posted...
Kind regards
--
rvangeldrop
[quoted text, click to view] "Kevin Yu [MSFT]" wrote:
> Hi Robbert,
>
> 1. Yes, this might be the firewall issue. But I can't be sure.
> 2. The the proxy object is actually a connection to the web service.
> Whether to pool it depends on your app. Generally, I suggest you use a new
> object to release the resources, if it is not called again and again. HTH.
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
>
Hi,
If there is similar issue, and I find a resolution, I will let you know.
Kevin Yu
Microsoft Online Community Support
============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Don't see what you're looking for? Try a search.
