Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / XML / April 2006

Tip: Looking for answers? Try searching our database.

persisent timeout problem consuming webservice

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Robbert van Geldrop - 30 Mar 2006 11:37 GMT
Hello,

I have a problem in a C# client that consumes a webservice which is wrapped
by WSE 2.0 sp3:

The WebService works fine but very rarely my client comes in a state where
every call to the webservice results in a timeout exception. Meanwhile all my
other internet traffic passes normally so the problem implicitly exists
between my client and the WebService.

The problem is solved as soon as the client is restarted.

I have two questions:
1. What can cause this problem?
2. What is the best way to solve this?

kind regards

Signature

rvangeldrop

Kevin Yu [MSFT] - 31 Mar 2006 08:32 GMT
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
Signature

=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

rvangeldrop@newsgroups.nospam - 31 Mar 2006 09:23 GMT
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,

> Hi,
>
[quoted text clipped - 10 lines]
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
Kevin Yu [MSFT] - 04 Apr 2006 08:30 GMT
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
Signature

=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Robbert van Geldrop - 07 Apr 2006 09:36 GMT
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
Signature

rvangeldrop

> Hi,
>
[quoted text clipped - 11 lines]
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
Kevin Yu [MSFT] - 10 Apr 2006 10:05 GMT
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
Signature

=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Robbert van Geldrop - 25 Apr 2006 14:31 GMT
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

Signature

rvangeldrop

> Hi Robbert,
>
[quoted text clipped - 7 lines]
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."
Kevin Yu [MSFT] - 27 Apr 2006 08:59 GMT
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.)

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.