Yes, It happens when the duration takes too long. It is probably only a very small amount, but it can happen. I fixed this locally and will push it up shortly.
On Fri, Oct 9, 2009 at 8:40 PM, Jason Meckley <[email protected]>wrote: > > System.ArgumentOutOfRangeException: Number must be either non-negative > and less than or equal to Int32.MaxValue or -1. > Parameter name: timeout > at System.Threading.Monitor.Wait(Object obj, TimeSpan timeout) > at Rhino.Queues.QueueManager.Receive(String queueName, String > subqueue, TimeSpan timeout) in QueueManager.cs: line 369 > at Rhino.Queues.QueueManager.Receive(String queueName, TimeSpan > timeout) in QueueManager.cs: line 343 > at Rhino.ServiceBus.RhinoQueues.RhinoQueuesTransport.ReceiveMessage() > in ....\Rhino.ServiceBus\RhinoQueues\RhinoQueuesTransport.cs: line 153 > at System.Threading.ThreadHelper.ThreadStart_Context(Object state) > at System.Threading.ExecutionContext.Run(ExecutionContext > executionContext, ContextCallback callback, Object state) > at System.Threading.ThreadHelper.ThreadStart() > > This happens, inconsistantly, in our production environment. I cannot > reproduce this in a test environment though. reviewing the > QueueManager.Recieve member it would seem the error occurs because as > some point line 331 > (remaining = remaining - sp.Elapsed;) makes remaining negative. > > At which point the system crashes, and the error is recorded to the > event log. Once I find out the service stopped. I log on, restart the > service, and the messages filter through. > > Any ideas on what may be causing negative time? > > the > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
