Re: BeginInvoke freezes
- From: "William Stacey [MVP]" <william.stacey@xxxxxxxxx>
- Date: Tue, 11 Apr 2006 20:03:01 -0400
I assume by your description that you call BeginInvoke on the UI thread. Is
there a reason your doing this? As shown this will "freeze" your UI for any
long running operation like waiting for a network reply so no other events
are processed on UI Q until return or DoEvents(). I would just use a worker
thread and only post back results to the UI after success/failure/progress.
--
William Stacey [MVP]
<leonard.guillaume@xxxxxxxxx> wrote in message
news:1144414186.639268.33330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
| Hi,
|
| I'm having random problems with BeginInvoke function. I have 2
| WebServices (VB.Net), the first one is the main ws and the second is
| the backup in case that the primary server crash or goes offline.
|
| My client, which is also in VB.Net tries to connect to the first
| webservice and has a timeout of 60 seconds. If it can't connect, it
| tries on the backup. The timeout is 60seconds because I'm using a
| 56kmodem.
|
| The problem is that randomly, the function BeginInvoke, which I use to
| call my WS async will freezes. Sometimes, the primary ws will respond
| correctly, but the backup will crash. Sometimes they both freezes
| BeginInvoke...anyway you see my point. It's very hard to debug
| somethings that is random and all the data my client is sending to the
| ws are valid. The BeginInvoke freezing gets my client GUI to freeze.
|
| Any hints ?
|
| Thanks :)
|
| Guillaume L.
|
.
- References:
- BeginInvoke freezes
- From: leonard . guillaume
- BeginInvoke freezes
- Prev by Date: .Net Framework 2.0 Installation Issues --- URGENT
- Next by Date: Re: Identify .NET Framework version
- Previous by thread: Re: BeginInvoke freezes
- Next by thread: Re: Creating DNF for a logical Term
- Index(es):
Relevant Pages
|