| Groups | Blog | Home |
dotnet web services : Preserving static variables in web services.
This class is called from a webservice. I donot create a socket for each request . the socket is created and connected to the target address for the first request.The subsequent requests each utilize the same socket. I have utilized mutexes around the static variable for any operations.The class which contains the socket variable is made singleton. The problems that I am currently facing is that the static socket variable is getting lost after about 30 minutes of inactivity. The network is not causing this problem. since this is executed under aspnet worker process and I have a feeling that the aspnet worker process is causing this problem. the question is how can I preserve static variables in aspnet worker process. The webservice is hosted under IIS 5.0 and is made as a separte application
Hello John
Thanks for the quick reply. Is there any event or code that I can write in my webservice to close the socket gracefully when the appdomain is being destroyed? I would like the socket to be closed because there is a limit on the number or sockets that I can open to the remote system. Thanks [quoted text, click to view] "John Saunders [MVP]" wrote:
> "biztalk2006" <biztalk2006@discussions.microsoft.com> wrote in message > news:A463B83E-DB0D-43B5-B1AE-B0FCD136ED4E@microsoft.com... > >I have a static variable in my class that contains a socket connection. > > This class is called from a webservice. I donot create a socket for each > > request . > > the socket is created and connected to the target address for the first > > request.The subsequent requests each utilize the > > same socket. > > I have utilized mutexes around the static variable for any operations.The > > class which contains the socket variable is made > > singleton. > > The problems that I am currently facing is that the static socket variable > > is getting lost after about > > 30 minutes of inactivity. > > The network is not causing this problem. since this is executed under > > aspnet > > worker process and > > I have a feeling that the aspnet worker process is causing this problem. > > the question is how can I preserve static variables in aspnet worker > > process. > > The webservice is hosted under IIS 5.0 and is made as a separte > > application > > in IIS. > > Static variables are scoped to the AppDomain in which they are created. When > the AppDomain id destroyed, the variables are also destroyed. > > Your best option is to not depend on the variable always being initialized. > If you find that the socket is null, reinitialize it. > -- > -------------------------------------------------------------------------------- > John Saunders | MVP - Windows Server System - Connected System Developer > >
[quoted text, click to view]
"biztalk2006" <biztalk2006@discussions.microsoft.com> wrote in message news:A463B83E-DB0D-43B5-B1AE-B0FCD136ED4E@microsoft.com... >I have a static variable in my class that contains a socket connection. > This class is called from a webservice. I donot create a socket for each > request . > the socket is created and connected to the target address for the first > request.The subsequent requests each utilize the > same socket. > I have utilized mutexes around the static variable for any operations.The > class which contains the socket variable is made > singleton. > The problems that I am currently facing is that the static socket variable > is getting lost after about > 30 minutes of inactivity. > The network is not causing this problem. since this is executed under > aspnet > worker process and > I have a feeling that the aspnet worker process is causing this problem. > the question is how can I preserve static variables in aspnet worker > process. > The webservice is hosted under IIS 5.0 and is made as a separte > application > in IIS. Static variables are scoped to the AppDomain in which they are created. When the AppDomain id destroyed, the variables are also destroyed. Your best option is to not depend on the variable always being initialized. If you find that the socket is null, reinitialize it. -- -------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer
Hello John
After careful analysis, I have come to the conclusion that the value in my static variable is preserved but the socket is becoming inactive meaning I am not able to send any data over the socket after 30 minutes of inactivity. It shows as established when I run netstat -na but when I tried to receive any data it throws me an exception saying that the remote host has forcibly closed the connection. This leads me to believe that tcp sockets have an idle time out . do you have any increasing the idletime out of tcp sockets or keeping alive the socket. I was reading on keep alive but it can not be used for client sockets. Let me know if you have any information on how to increase the idle time out of the socket [quoted text, click to view] "biztalk2006" wrote:
> Hello John > Thanks for the quick reply. Is there any event or code that I can write in > my webservice to close the socket gracefully when the appdomain is being > destroyed? > I would like the socket to be closed because there is a limit on the number > or sockets that I can open to the remote system. > Thanks > > > "John Saunders [MVP]" wrote: > > > "biztalk2006" <biztalk2006@discussions.microsoft.com> wrote in message > > news:A463B83E-DB0D-43B5-B1AE-B0FCD136ED4E@microsoft.com... > > >I have a static variable in my class that contains a socket connection. > > > This class is called from a webservice. I donot create a socket for each > > > request . > > > the socket is created and connected to the target address for the first > > > request.The subsequent requests each utilize the > > > same socket. > > > I have utilized mutexes around the static variable for any operations.The > > > class which contains the socket variable is made > > > singleton. > > > The problems that I am currently facing is that the static socket variable > > > is getting lost after about > > > 30 minutes of inactivity. > > > The network is not causing this problem. since this is executed under > > > aspnet > > > worker process and > > > I have a feeling that the aspnet worker process is causing this problem. > > > the question is how can I preserve static variables in aspnet worker > > > process. > > > The webservice is hosted under IIS 5.0 and is made as a separte > > > application > > > in IIS. > > > > Static variables are scoped to the AppDomain in which they are created. When > > the AppDomain id destroyed, the variables are also destroyed. > > > > Your best option is to not depend on the variable always being initialized. > > If you find that the socket is null, reinitialize it. > > -- > > -------------------------------------------------------------------------------- > > John Saunders | MVP - Windows Server System - Connected System Developer > > > >
[quoted text, click to view]
"biztalk2006" <biztalk2006@discussions.microsoft.com> wrote in message news:29533A51-37F1-4691-BE3F-32B86FFFA6EA@microsoft.com... > Hello John > After careful analysis, I have come to the conclusion that the value in my > static variable is preserved but the socket is becoming inactive meaning I > am > not able to send any data over the socket after 30 minutes of inactivity. > It > shows as established when I run netstat -na but when I tried to receive > any > data it throws me an exception saying that the remote host has forcibly > closed the connection. This leads me to believe that tcp sockets have an > idle > time out . do you have any increasing the idletime out of tcp sockets or > keeping alive the socket. I was reading on keep alive but it can not be > used > for client sockets. Let me know if you have any information on how to > increase the idle time out of the socket Actually, I think you're making a mistake with this approach, period. A web service is not the same thing as a Windows Service. It's not something that starts up when the system starts, and just keeps running. You should not expect your socket, or anything else, to just hang around in memory and/or the process, waiting for something to happen. You should create a simple Windows Service for this, and connect the two via ..NET Remoting, or WCF. The service won't have any problem with the socket closing, as the service will always be running. -- -------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |