Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4249
  • Last Modified:

WebService Timeout

Struggling with timeouts on a webservice - not sure if it from client or server....

I have a long-running job (about 10 minutes) that I need to run in ASP.NET. I am using a webservice call to initiate the job in a client app:

        Dim t As New webschedule.com.domain.www.schedjobs
        t.Timeout = 120000
        EventLog1.WriteEntry("returned: " & CStr(DateTime.Now) & t.writexmljob)

On the server I have the web service.

In web.config I have increased the execution timeout:

<httpRuntime executionTimeout="720000" />

and still I get:

System.Net.WebException
  Message="The operation has timed out"
  Source="System.Web.Services"

What to do? any pointers would be much appreciated. I just need a simple, scheduled mechanism to run a job within ASP.NET that works consistently.

Thanks
0
ctudorprice
Asked:
ctudorprice
  • 3
1 Solution
 
kulkarnivishwajitCommented:
There are two places you may have to change:

1. Change the ASP.NET timeout, not ASP one:

http://www.devx.com/vb2themax/Tip/18803

This is the most likely culprit of your errors

2. Use the Timeout property of your proxy class to set the proper time on
the client.

WebReference.ProxyClass myProxy = new WebReference.ProxyClass();
// Set the timeout in milliseconds -- e.g. 100 seconds
myProxy.Timeout = 100000;

Hope that helps.

Regards,
kulkarnivishwajit
0
 
ctudorpriceAuthor Commented:
hmm, i've read that advice before (verbatim)... in fact, here: http://www.thescripts.com/forum/thread426335.html

...and the executionTimeout is the aspx timeout. My question wasn't the same as the question in the link above.

Can anyone else help?

The job times-out after exactly 2 minutes.
0
 
ctudorpriceAuthor Commented:
Just in case anyone else runs into this:
I turned off Process Pinging in the IIS Application Pool configuration and the problem was resolved. Basically, IIS pings the worker process periodically and if it doesn't respond, kills it and restarts it. Obvious now I've found it... but took me 3 days of hunting, googling, tweaking, testing and wasting time to eventually find it.
Sadly, this is a mystery because there is no logging in the event that IIS decides to kill a process (because it didn't respond) - it just disappears for no apparent reason. Jeez - you'd think the venerable folks at Microsoft would know better.... Had there been a log entry, this might have take 5 minutes to figure out.


0
 
ctudorpriceAuthor Commented:
I'm going to award some points so this question is closed. But kulkarnivishwajit's answer isn't the right one in this case...
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now