I am developing an application using VB .NET and Remoting. When the application is not used for a few minutes it seems to lock up. In Task Manager is shows as running. Any ideas are appreciated!
In Remoting, the object you created , will be destroyed if you have not been using it for some. This is probably the cause of your application lock up. Try set the object mode for your remoting object as singleton or set the InitializeLifetimeService for the object to return nothing...
Public Overrides Function InitializeLifetimeService() As Object Return Nothing End Function
I did some additional research and found some scalability issues with the HTTP Keep-Alive setting in IIS. I had it turned on with a timeout of two minutes. This coresponded with the time frame the application was locking up in. Once turned off my application stopped locking up but there was a noticible drop in perfomance (although minimal).
It is my understanding that the keep alive attribute essentially keeps a connection open to the website (In my case a remoted object). This does not make sense, at least to me that the application did not work once the connection timed out but works fine (except for a slight performance drop) when the connection is droped immediately after use. Does anyone have some insight
Application Locks Up
KalliMan
Ravindra Agrawal
Public Overrides Function InitializeLifetimeService() As Object
Return Nothing
End Function
rubnov
It is my understanding that the keep alive attribute essentially keeps a connection open to the website (In my case a remoted object). This does not make sense, at least to me that the application did not work once the connection timed out but works fine (except for a slight performance drop) when the connection is droped immediately after use. Does anyone have some insight