[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

Bug in IIS hosting of Remote Objects?

dinesh336

7/19/2004 8:48:00 PM

Hello,

I have a Singleton Remoting Object hosted inside IIS. It has a sponsor
in a Windows Service that renews the lease. So as long as the Windows
Service is running I expect the remoting object to stay within scope.

However I find that it is not the case. The Singleton object goes out
of scope in a random fashion - sometimes once in a couple of days and
sometimes thrice within an hour. Even though it goes out of scope it
remains in memory (I know this because of the debug messages). I
double checked the code and made sure there are no uncaught
exceptions.

Is is possible that there is some kind of bug in the way IIS hosts
remoting objects? Has anyone else encountered similar behavior?

Appreciate any thoughts on this matter,

Dinesh
4 Answers

Sunny

7/19/2004 9:18:00 PM

0

Hi,

IIS can recycle the aspnet process for a different reasons, thats why
you see that behaviour.

In general, to avoid this, you can disable the process recycling. For
IIS 5.0, you have to modify the <processModel> section in
machine.config. For IIS 6.0, by setting the properties on the
Application Pool in which your web app runs.

Also, make sure that no process is modifying the files in the web app
folder, or in Windows\Microsoft.NET\Framework\v1.1.4322\CONFIG. Any
modification in these folders may cause a process restart.

Sunny

In article <727ca83c.0407191247.211e65fe@posting.google.com>, dinesh336
@hotmail.com says...
> Hello,
>
> I have a Singleton Remoting Object hosted inside IIS. It has a sponsor
> in a Windows Service that renews the lease. So as long as the Windows
> Service is running I expect the remoting object to stay within scope.
>
> However I find that it is not the case. The Singleton object goes out
> of scope in a random fashion - sometimes once in a couple of days and
> sometimes thrice within an hour. Even though it goes out of scope it
> remains in memory (I know this because of the debug messages). I
> double checked the code and made sure there are no uncaught
> exceptions.
>
> Is is possible that there is some kind of bug in the way IIS hosts
> remoting objects? Has anyone else encountered similar behavior?
>
> Appreciate any thoughts on this matter,
>
> Dinesh
>

dinesh336

7/20/2004 3:36:00 PM

0

OK. Thank you for clearing this issue.

You say I can modify the IIS 6.0 settings Application Pool. Is it
something that needs to be done programmatically or using IIS Admin?
If possible, can you please point me to any articles that talks about
this.

What is the downside to disable process recycling?

Thanks,
Dinesh


Sunny <sunny@newsgroups.nospam> wrote in message news:<uStlWXdbEHA.4092@TK2MSFTNGP11.phx.gbl>...
> Hi,
>
> IIS can recycle the aspnet process for a different reasons, thats why
> you see that behaviour.
>
> In general, to avoid this, you can disable the process recycling. For
> IIS 5.0, you have to modify the <processModel> section in
> machine.config. For IIS 6.0, by setting the properties on the
> Application Pool in which your web app runs.
>
> Also, make sure that no process is modifying the files in the web app
> folder, or in Windows\Microsoft.NET\Framework\v1.1.4322\CONFIG. Any
> modification in these folders may cause a process restart.
>
> Sunny
>
> In article <727ca83c.0407191247.211e65fe@posting.google.com>, dinesh336
> @hotmail.com says...
> > Hello,
> >
> > I have a Singleton Remoting Object hosted inside IIS. It has a sponsor
> > in a Windows Service that renews the lease. So as long as the Windows
> > Service is running I expect the remoting object to stay within scope.
> >
> > However I find that it is not the case. The Singleton object goes out
> > of scope in a random fashion - sometimes once in a couple of days and
> > sometimes thrice within an hour. Even though it goes out of scope it
> > remains in memory (I know this because of the debug messages). I
> > double checked the code and made sure there are no uncaught
> > exceptions.
> >
> > Is is possible that there is some kind of bug in the way IIS hosts
> > remoting objects? Has anyone else encountered similar behavior?
> >
> > Appreciate any thoughts on this matter,
> >
> > Dinesh
> >

Sunny

7/20/2004 3:58:00 PM

0

Hi,

check these links:

http://www.dotnetindia.com/2003/10/why_aspnet...

http://www.codeproject.com/aspnet...
(this is for IIS 5.o, but will give you some ideas)

http://www.developer.com/net/asp/article.p...
this explains how asp.net process runs under IIS 6.0


Sunny


In article <727ca83c.0407200735.62042815@posting.google.com>, dinesh336
@hotmail.com says...
> OK. Thank you for clearing this issue.
>
> You say I can modify the IIS 6.0 settings Application Pool. Is it
> something that needs to be done programmatically or using IIS Admin?
> If possible, can you please point me to any articles that talks about
> this.
>
> What is the downside to disable process recycling?
>
> Thanks,
> Dinesh
>
>
> Sunny <sunny@newsgroups.nospam> wrote in message news:<uStlWXdbEHA.4092@TK2MSFTNGP11.phx.gbl>...
> > Hi,
> >
> > IIS can recycle the aspnet process for a different reasons, thats why
> > you see that behaviour.
> >
> > In general, to avoid this, you can disable the process recycling. For
> > IIS 5.0, you have to modify the <processModel> section in
> > machine.config. For IIS 6.0, by setting the properties on the
> > Application Pool in which your web app runs.
> >
> > Also, make sure that no process is modifying the files in the web app
> > folder, or in Windows\Microsoft.NET\Framework\v1.1.4322\CONFIG. Any
> > modification in these folders may cause a process restart.
> >
> > Sunny
> >
> > In article <727ca83c.0407191247.211e65fe@posting.google.com>, dinesh336
> > @hotmail.com says...
> > > Hello,
> > >
> > > I have a Singleton Remoting Object hosted inside IIS. It has a sponsor
> > > in a Windows Service that renews the lease. So as long as the Windows
> > > Service is running I expect the remoting object to stay within scope.
> > >
> > > However I find that it is not the case. The Singleton object goes out
> > > of scope in a random fashion - sometimes once in a couple of days and
> > > sometimes thrice within an hour. Even though it goes out of scope it
> > > remains in memory (I know this because of the debug messages). I
> > > double checked the code and made sure there are no uncaught
> > > exceptions.
> > >
> > > Is is possible that there is some kind of bug in the way IIS hosts
> > > remoting objects? Has anyone else encountered similar behavior?
> > >
> > > Appreciate any thoughts on this matter,
> > >
> > > Dinesh
> > >
>

dinesh336

7/21/2004 2:26:00 PM

0

Very useful links. Thanks a lot.

Sunny <sunny@newsgroups.nospam> wrote in message news:<OR$HaJnbEHA.1764@TK2MSFTNGP10.phx.gbl>...
> Hi,
>
> check these links:
>
> http://www.dotnetindia.com/2003/10/why_aspnet...
>
> http://www.codeproject.com/aspnet...
> (this is for IIS 5.o, but will give you some ideas)
>
> http://www.developer.com/net/asp/article.p...
> this explains how asp.net process runs under IIS 6.0
>
>
> Sunny
>
>
> In article <727ca83c.0407200735.62042815@posting.google.com>, dinesh336
> @hotmail.com says...
> > OK. Thank you for clearing this issue.
> >
> > You say I can modify the IIS 6.0 settings Application Pool. Is it
> > something that needs to be done programmatically or using IIS Admin?
> > If possible, can you please point me to any articles that talks about
> > this.
> >
> > What is the downside to disable process recycling?
> >
> > Thanks,
> > Dinesh
> >
> >
> > Sunny <sunny@newsgroups.nospam> wrote in message news:<uStlWXdbEHA.4092@TK2MSFTNGP11.phx.gbl>...
> > > Hi,
> > >
> > > IIS can recycle the aspnet process for a different reasons, thats why
> > > you see that behaviour.
> > >
> > > In general, to avoid this, you can disable the process recycling. For
> > > IIS 5.0, you have to modify the <processModel> section in
> > > machine.config. For IIS 6.0, by setting the properties on the
> > > Application Pool in which your web app runs.
> > >
> > > Also, make sure that no process is modifying the files in the web app
> > > folder, or in Windows\Microsoft.NET\Framework\v1.1.4322\CONFIG. Any
> > > modification in these folders may cause a process restart.
> > >
> > > Sunny
> > >
> > > In article <727ca83c.0407191247.211e65fe@posting.google.com>, dinesh336
> > > @hotmail.com says...
> > > > Hello,
> > > >
> > > > I have a Singleton Remoting Object hosted inside IIS. It has a sponsor
> > > > in a Windows Service that renews the lease. So as long as the Windows
> > > > Service is running I expect the remoting object to stay within scope.
> > > >
> > > > However I find that it is not the case. The Singleton object goes out
> > > > of scope in a random fashion - sometimes once in a couple of days and
> > > > sometimes thrice within an hour. Even though it goes out of scope it
> > > > remains in memory (I know this because of the debug messages). I
> > > > double checked the code and made sure there are no uncaught
> > > > exceptions.
> > > >
> > > > Is is possible that there is some kind of bug in the way IIS hosts
> > > > remoting objects? Has anyone else encountered similar behavior?
> > > >
> > > > Appreciate any thoughts on this matter,
> > > >
> > > > Dinesh
> > > >
> >