Do you have access to the server? A thought is that the server is maxing out its limit of connections and isn't closing them. That could the reason that once it breaks once, it continues to break.
If you restart your program does it start working again? If so then it's obviously something with you application, otherwise there's not much you can do about it because it's probably the server. What type of connection are you making? (WCF, Http web request, etc.) On Sep 3, 12:21 pm, "Joseph Irizarry" <[EMAIL PROTECTED]> wrote: > I agree with Brandon, through it doesn't seem likely, but disposing the > connection could help.A code snippet would help us with debugging. > > On Wed, Sep 3, 2008 at 11:30 AM, Brandon Betances <[EMAIL PROTECTED]>wrote: > > > > > Close the connection before the timer starts again? Just a thought > > > On 9/2/08, weiran <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > What's the best way to repetitively request a response from a remote > > > server that is not 100% reliable? I'm currently using a timer set to > > > fire every three minutes that creates a connection and tries to > > > receive a response, but it seems sometimes if the connection times > > > out, every subsequent connection attempt also times out. I'm not sure > > > what to do about this? > > > > Thanks, > > > Weiran. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to DotNetDevelopment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
