Bug 2084 - Unhandled ArgumentOutOfRangeException on WCF REST service
Summary: Unhandled ArgumentOutOfRangeException on WCF REST service
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: WCF assemblies (show other bugs)
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-11-17 23:05 UTC by John Hargrove
Modified: 2011-11-17 23:05 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 2084 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description John Hargrove 2011-11-17 23:05:58 UTC
I am running mono 2.10.2 on OpenSUSE 11.4 x86-64.

I have a WCF-based service that responds to WebGet requests. Occasionally, and almost always when executing a particularly long request, my application will crash and an unhandled exception will be dumped to STDERR.

The service may run for days without encountering this problem. The exception looks like this:

Unhandled Exception: System.ArgumentOutOfRangeException: Argument is out of range.
Parameter name: timeout
  at System.Threading.WaitHandle.WaitOne (TimeSpan timeout, Boolean exitContext) [0x00000] in <filename unknown>:0
  at System.Threading.WaitHandle.WaitOne (TimeSpan timeout) [0x00000] in <filename unknown>:0
  at System.ServiceModel.Channels.Http.HttpListenerManager.TryDequeueRequest (System.ServiceModel.Dispatcher.ChannelDispatcher channel, TimeSpan timeout, System.ServiceModel.Channels.Http.HttpContextInfo& context) [0x00000] in <filename unknown>:0
  at System.ServiceModel.Channels.Http.HttpListenerManager.TryDequeueRequest (System.ServiceModel.Dispatcher.ChannelDispatcher channel, TimeSpan timeout, System.ServiceModel.Channels.Http.HttpContextInfo& context) [0x00000] in <filename unknown>:0
  at System.ServiceModel.Channels.Http.HttpReplyChannel.TryReceiveRequest (TimeSpan timeout, System.ServiceModel.Channels.RequestContext& context) [0x00000] in <filename unknown>:0
  at System.ServiceModel.Channels.ReplyChannelBase.<BeginTryReceiveRequest>m__1A (TimeSpan tout, System.ServiceModel.Channels.RequestContext& ctx) [0x00000] in <filename unknown>:0

I have not determined a workaround. I can say that this -seems- more likely to happen during long-lasting requests, such as those which return a large amount of data over a slow VPN connection. This would suggest to me that this may be related to multiple concurrent requests to a service, but that's speculative.