Ramon Leon wrote:
>> Then I need you to debug some more stuff:
>>
>> 1) Which VM are you using?
>>     
>
>   
If the millisecondClock is close to rolling over then the deadline may 
be set in the future to a number greater than SmallInteger maxVal and 
timeouts will never complete.

For Socket the default timeout is 45 seconds. So thinking about it this 
error is only likely to occur for 45 seconds every 12 days or so, but it 
will occur if there is code which relies upon the timeout itself.

Now this is a complete guess but it might be your explanation. What if 
somehow your millisecond clock has failed to roll over and might be 
stuck in that dangerous region ie. at SmallInteger maxVal.

Keith




		
___________________________________________________________ 
Try the all-new Yahoo! Mail. "The New Version is radically easier to use" – The Wall Street Journal 
http://uk.docs.yahoo.com/nowyoucan.html