Waspman
Posts: 948
|
| Posted: 08/04/2006, 4:03 AM |
|
According to this fella...
http://blogs.msdn.com/david.wang/archive/2005/09/19/Why...te_on_IIS6.aspx
...it looks like we can't control the session timeout using code (i think that's what he's saying)
Having wrestled with this one for a over a year and very little help from Hostway( ) our clients preferred host, I'm now iframing a page in the footer which refreshes itself after a given time and the session stops open.
_________________
http://www.waspmedia.co.uk |
 |
 |
peterr
Posts: 5971
|
| Posted: 08/04/2006, 12:10 PM |
|
We use 24 hour session timeout in our support system (http://support.yessoftware.com/support_new.asp ), which is set using Session.Timeout.
Possibly sessions are lost occasionally without known reason but I never noticed this. Thus I don't think that this is very noticable problem.
Are you unable to control session timeout at all? For example does it never work beyond X seconds for you?
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
Waspman
Posts: 948
|
| Posted: 08/04/2006, 12:22 PM |
|
No, despite a liberal use of the session.timeout = 1440, we loose session after very short periods, which vary.
I have to say that it has never worked for us and I thought that the blog by David Wang explained why?
_________________
http://www.waspmedia.co.uk |
|
|
|
peterr
Posts: 5971
|
| Posted: 08/04/2006, 12:47 PM |
|
I don't fully understand where David is coming from, and it seems to me that he may be referring to some sporadical problems that occur once in a while on certain servers. ASP has been around for years and I don't even see how it's possible that anyone could use ASP for all those years with a major problem of this type. Many popular shopping Websites (including Microsoft's) were written in ASP before .NET came out, and I don't remember anyone complaining about losing their shopping cart contents, for example. And why would the Session.Timeout property exist in ASP at all? Such issue would probably quickly become the most frequently discussed problem on the Internet and ASP would never be usable.
Possibly the problem is related only to IIS6. I just checked my XP Pro and I have IIS 5.1, for example. I also don't see the w3wp.exe process running on my computer.
I also recommend that you test the application on your own computer to confirm the problem, and set the timeout to about 30 minutes instead of 1440 during testing.
Maybe try another hosting company as well, just to show to your client that the application works fine elsewhere - if it indeed does.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
DonB
|
| Posted: 08/04/2006, 9:05 PM |
|
And I'd check the system/application Event logs. One of them(forget which
is it, but I think 'applicaton') may show 'IIS has stopped unexpectedly'
errors. It does that and restarts itself without you noticing it (most of
the time). That could be the real culprit.
--
DonB
http://www.gotodon.com/ccbth
"peterr" <peterr@forum.codecharge> wrote in message
news:644d3a46e6ddac@news.codecharge.com...
> I don't fully understand where David is coming from, and it seems to me
that he
> may be referring to some sporadical problems that occur once in a while on
> certain servers. ASP has been around for years and I don't even see how
it's
> possible that anyone could use ASP for all those years with a major
problem of
> this type. Many popular shopping Websites (including Microsoft's) were
written
> in ASP before .NET came out, and I don't remember anyone complaining about
> losing their shopping cart contents, for example. And why would the
> Session.Timeout property exist in ASP at all? Such issue would probably
quickly
> become the most frequently discussed problem on the Internet and ASP would
never
> be usable.
>
> Posisbly the problem is related only to IIS6. I just checked my XP Pro
and I
> have IIS 5.1, for example. I also don't see the w3wp.exe process running
on my
> computer.
>
> I also recommend that you test the application on your own computer to
confirm
> the problem, and set the timeout to about 30 minutes instead of 1440
during
> testing.
> Maybe try another hosting company as well, just to show to your client
that the
> application works fine elsewhere - if it indeed does.
> _________________
> Peter R.
> YesSoftware Forums Moderator
> For product support please visit http://support.yessoftware.com
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
Waspman
Posts: 948
|
| Posted: 08/05/2006, 11:26 AM |
|
Sorted!
My new host (Protec) moved my domain to an application pool with daily recyling.
Thanks guys
_________________
http://www.waspmedia.co.uk |
|
|
|
|
