web service call locks up C# winforms application

[=?Utf-8?B?Y2hlbmRyaWNrcw==?=]

I have a C# winforms application that makes periodic web service calls in
background thread to my web service server. These calls work fine almost all
the time but on rare occassions the web service method call will never return
and the entire application will freeze, even though the call is being made on
its own background thread, not the main UI thread.

Does anyone know any reason why a particular web service method call would
cause my entire C# application to lock up and become unresponsive? Again,
this call is initiated on a background thread and this thread does not
interact with the main UI thread at all.

Thanks for any ideas,

Colin

[John Saunders [MVP]]

"chendricks" <ch********@discussions.microsoft.comwrote in message
news:58**********************************@microsof t.com...

>I have a C# winforms application that makes periodic web service calls in
background thread to my web service server. These calls work fine almost
all
the time but on rare occassions the web service method call will never
return
and the entire application will freeze, even though the call is being made
on
its own background thread, not the main UI thread.

Does anyone know any reason why a particular web service method call would
cause my entire C# application to lock up and become unresponsive? Again,
this call is initiated on a background thread and this thread does not
interact with the main UI thread at all.

Obviously, there _is_ interaction with the UI thread. This interaction may
not be direct, but if there were no such interaction, I don't see how the UI
thread could freeze.

Does this happen when you run in the debugger? If so, can you break
execution when the freeze happens and use the Call Stack to find out where
the UI thread is blocking?
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

[=?Utf-8?B?Y2hlbmRyaWNrcw==?=]

I am unable to reproduce this at all either in the debugger or not. This
application runs on about 600 client machines and runs 24x7. The freeze
happens on about 1 machine about every other day.

My web service method is called "heartbeat" and all it does is let my server
know that the client is still alive. The client thread that calls the
heartbeat method does nothing else but call the method, then sleep for 5
minutes, then call it again. It's just a simple loop. It doesn't interact
with the main UI thread.

Other than manipulating a GUI control on the main UI thread, which I know is
bad, is there anything else related to WS calls that might freeze the
application?

Thanks for your help,

Colin

"John Saunders [MVP]" wrote:

"chendricks" <ch********@discussions.microsoft.comwrote in message
news:58**********************************@microsof t.com...

I have a C# winforms application that makes periodic web service calls in
background thread to my web service server. These calls work fine almost
all
the time but on rare occassions the web service method call will never
return
and the entire application will freeze, even though the call is being made
on
its own background thread, not the main UI thread.

Does anyone know any reason why a particular web service method call would
cause my entire C# application to lock up and become unresponsive? Again,
this call is initiated on a background thread and this thread does not
interact with the main UI thread at all.

Obviously, there _is_ interaction with the UI thread. This interaction may
not be direct, but if there were no such interaction, I don't see how the UI
thread could freeze.

Does this happen when you run in the debugger? If so, can you break
execution when the freeze happens and use the Call Stack to find out where
the UI thread is blocking?
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

[Andrew Faust]

Does it share any resources that are used by other threads? Any variables,
database connections, files or any other resources that you are locking
while this task is processing? It sounds like you could have two threads
that need access to the same shared resource and they are running in to a
deadlocking situation. That would also explain why it's so hard to
reproduce.

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com
"chendricks" <ch********@discussions.microsoft.comwrote in message
news:60**********************************@microsof t.com...

>I am unable to reproduce this at all either in the debugger or not. This
application runs on about 600 client machines and runs 24x7. The freeze
happens on about 1 machine about every other day.

My web service method is called "heartbeat" and all it does is let my
server
know that the client is still alive. The client thread that calls the
heartbeat method does nothing else but call the method, then sleep for 5
minutes, then call it again. It's just a simple loop. It doesn't interact
with the main UI thread.

Other than manipulating a GUI control on the main UI thread, which I know
is
bad, is there anything else related to WS calls that might freeze the
application?

Thanks for your help,

Colin

"John Saunders [MVP]" wrote:

>"chendricks" <ch********@discussions.microsoft.comwrote in message
news:58**********************************@microso ft.com...

>I have a C# winforms application that makes periodic web service calls
in
background thread to my web service server. These calls work fine
almost
all
the time but on rare occassions the web service method call will never
return
and the entire application will freeze, even though the call is being
made
on
its own background thread, not the main UI thread.

Does anyone know any reason why a particular web service method call
would
cause my entire C# application to lock up and become unresponsive?
Again,
this call is initiated on a background thread and this thread does not
interact with the main UI thread at all.

Obviously, there _is_ interaction with the UI thread. This interaction
may
not be direct, but if there were no such interaction, I don't see how
the UI
thread could freeze.

Does this happen when you run in the debugger? If so, can you break
execution when the freeze happens and use the Call Stack to find out
where
the UI thread is blocking?
--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer