I've been asked to find out why it takes 20 seconds before the socket
is closed after a call to a SAO singleton or singlecall object.  Is it
possible to change this idle time figure?

On Aug 3, 5:19 pm, Justin__Bar...@Hotmail.Com wrote:


> I've been asked to find out why it takes 20 seconds before the socket
> is closed after a call to a SAO singleton or singlecall object.  Is it
> possible to change this idle time figure?


Technically that's not idle time, that's the channel living its life.
I bet you would take offence if someone was asked to find out why it
took 90 years for Justin to dispose.

Look up the documentation for InitializeLifetimeService on MSDN:
http://msdn2.microsoft.com/en-us/library/4th828yf.aspx

On 9 Aug, 22:09, UL-Tomten  wrote:

> On Aug 3, 5:19 pm, Justin__Bar...@Hotmail.Com wrote:
>
> > I've been asked to find out why it takes 20 seconds before the socket
> > is closed after a call to a SAO singleton or singlecall object.  Is it
> > possible to change this idle time figure?
>
> Technically that's not idle time, that's the channel living its life.
> I bet you would take offence if someone was asked to find out why it
> took 90 years for Justin to dispose.
>
> Look up the documentation for InitializeLifetimeService on MSDN:http://msdn2.microsoft.com/en-us/library/4th828yf.aspx


Hi

I've done this already and it is not relevant.  It has no bearing on
when the socket is closed.

Thanks for you help.
Justin

Justin__Barnes@Hotmail.Com schreef:

> On 9 Aug, 22:09, UL-Tomten  wrote:
>> On Aug 3, 5:19 pm, Justin__Bar...@Hotmail.Com wrote:
>>
>>> I've been asked to find out why it takes 20 seconds before the socket
>>> is closed after a call to a SAO singleton or singlecall object.  Is it
>>> possible to change this idle time figure?
>> Technically that's not idle time, that's the channel living its life.
>> I bet you would take offence if someone was asked to find out why it
>> took 90 years for Justin to dispose.
>>
>> Look up the documentation for InitializeLifetimeService on MSDN:http://msdn2.microsoft.com/en-us/library/4th828yf.aspx
> 
> Hi
> 
> I've done this already and it is not relevant.  It has no bearing on
> when the socket is closed.
> 
> Thanks for you help.
> Justin
> 


Maybe this is what you're looking for:

http://msdn2.microsoft.com/en-us/library/bb187436.aspx

See socketCacheTimeout, but it states it takes 5 seconds not 20

Many thanks.

I've tried this solution and it works ok.

I will continue to test it over the next few weeks.

This is great news.