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


 

Forums >

microsoft.public.dotnet.framework.remoting

SAO objects (single call) hosted in IIS 6 seem to "die" after a while?

Joe

7/13/2004 8:58:00 AM

I have a set of SAO (single call) objects hosted in IIS 6 on 2k3,
communicating over an HTTP channel from the client. The application runs
really well as long as I keep the application "busy" on a regular basis.
That is, it runs well as long as I click on something that requires a remote
method call "every so often". I believe that "every so often" is defined
around a few minutes.

If I don't click on something that requires a server round-trip for a
while, I get a WebException ("the operation has timed-out").

Any ideas? or is more information necessary?

The time between "tickling" the server seems to be in the range of 3 - 5
minutes for failure.


Thanks in advance,

Joe
3 Answers

Sunny

7/13/2004 2:54:00 PM

0

Hi,

in your Global.asax file put some logging in ApplicatonStart and
ApplicationEnd event handlers. Just see if IIS has restarted the process
before the timeout. If this is the case, than you have to extend the
timeout at the client side, the current one is not enough to wait for
the process start (the first call penalty :) )

Sunny

In article <0vNIc.5454$lG.1343@cyclops.nntpserver.com>,
spammersshouldbebeaten@iainttellin.com says...
> I have a set of SAO (single call) objects hosted in IIS 6 on 2k3,
> communicating over an HTTP channel from the client. The application runs
> really well as long as I keep the application "busy" on a regular basis.
> That is, it runs well as long as I click on something that requires a remote
> method call "every so often". I believe that "every so often" is defined
> around a few minutes.
>
> If I don''t click on something that requires a server round-trip for a
> while, I get a WebException ("the operation has timed-out").
>
> Any ideas? or is more information necessary?
>
> The time between "tickling" the server seems to be in the range of 3 - 5
> minutes for failure.
>
>
> Thanks in advance,
>
> Joe
>
>
>

Allen Anderson

7/15/2004 9:13:00 PM

0

check out this msdn article on leases and sponsors.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/introre...

Cheers,
Allen Anderson
http://www.glacialcomp...
mailto: allen@put my website base here.com

On Tue, 13 Jul 2004 16:57:52 +0800, "Joe"
<spammersshouldbebeaten@iainttellin.com> wrote:

>I have a set of SAO (single call) objects hosted in IIS 6 on 2k3,
>communicating over an HTTP channel from the client. The application runs
>really well as long as I keep the application "busy" on a regular basis.
>That is, it runs well as long as I click on something that requires a remote
>method call "every so often". I believe that "every so often" is defined
>around a few minutes.
>
>If I don''t click on something that requires a server round-trip for a
>while, I get a WebException ("the operation has timed-out").
>
>Any ideas? or is more information necessary?
>
>The time between "tickling" the server seems to be in the range of 3 - 5
>minutes for failure.
>
>
>Thanks in advance,
>
>Joe
>

Joe

7/21/2004 7:08:00 AM

0

Hi allen -

Thank you for your pointer. I am a little confused about one thing though.
My understanding (and the article I think) seems to infer that lifetime is
not an issue with SingleCall objects. As far as I can tell, Singlecall
objects are created/destroyed for every call.

I am getting a timeout exception, is that what happens when a lease runs
out?

Thank you in advance for your time,

Joe

"Allen Anderson" <allen@sparkysystems.com> wrote in message
news:tqsdf0p78a7150n7vjfta0vmk0e3cjfpsv@4ax.com...
> check out this msdn article on leases and sponsors.
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/introre...
>
> Cheers,
> Allen Anderson
> http://www.glacialcomp...
> mailto: allen@put my website base here.com
>
> On Tue, 13 Jul 2004 16:57:52 +0800, "Joe"
> <spammersshouldbebeaten@iainttellin.com> wrote:
>
> >I have a set of SAO (single call) objects hosted in IIS 6 on 2k3,
> >communicating over an HTTP channel from the client. The application runs
> >really well as long as I keep the application "busy" on a regular basis.
> >That is, it runs well as long as I click on something that requires a
remote
> >method call "every so often". I believe that "every so often" is defined
> >around a few minutes.
> >
> >If I don't click on something that requires a server round-trip for a
> >while, I get a WebException ("the operation has timed-out").
> >
> >Any ideas? or is more information necessary?
> >
> >The time between "tickling" the server seems to be in the range of 3 - 5
> >minutes for failure.
> >
> >
> >Thanks in advance,
> >
> >Joe
> >
>