| Author |
 Topic  |
|
RichardKinser
Snitz Forums Admin
USA
16655 Posts |
 Posted - 20 November 2004 : 05:21:35
|
| The difference is between IIS5 and IIS6. It is my understanding that IIS6 is pretty much a total rewrite, maybe there are some different configuration settings that need to be tweaked. |
 |
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 08:12:40
|
The only visible (well  ) error is that in IE the progress bar only gets to the 4th or 5th marker. There is nothing in the Event Log, and no ASP pages render until Gremlin recycles the application pool. |
|
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 08:23:45
|
quote:
the two objects mentioned by laser are opened so seldom that they would not cause a problem.
Fair enough, but I posted the problems so they could be fixed - your choice whether they are actually implemented in the code. Now that you have the general jist, I'll abbreviate a bit.
All these objects are not closed :
admin_config_order.asp : rsCount
admin_count.asp : Server2, or can we close it ?
admin_forums.asp : Server2, drs, delRep, rsTcheck
admin_login.asp : dbRs not (now that IS used a lot)
admin_login_short.asp : dbRs
admin_moderators.asp : rs
admin_mod_dbsetup.asp : objFile, objFolder, objFolderContents
inc_func_common.asp : strNTUserInfo
inc_mail.asp : iConf, Flds, gMDUser, gMDMessageInfo
pop_lock.asp : rs
pop_moderate.asp : rsSub
Now this is the "extra info" I was talking about. These MIGHT be related to MODs, but I'm concerned about the Server2 objects. I know it was added to get around a Brinkster hangup but that could be causing a larger issue
|
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
Posted - 20 November 2004 : 08:26:43
|
quote:
The only visible (well ) error is that in IE the progress bar only gets to the 4th or 5th marker. There is nothing in the Event Log, and no ASP pages render until Gremlin recycles the application pool.
Happened to me too. I eventually disabled recycling altogether and rapid fail protection.
The biggest (and hardest to fix) issue was the 5000 limit on local ports than w2003 has. If there is a lot of database activity this can cause similar errors to the one you experienced.
When you use a database connection (e.g. to sql server on port 1433) w2003 assigns a random port (below 5000) to the connection locally and 1433 remotely. Some of these connections are used more than once (connection pooling) but some connections end up in a wait state and don't die for about 4-5 minutes before they can be used again.
If you're looping through a recordset one port is opened for each iteration (some of them will be pooled) and you can use up the 5,000 limit rather easily.
Solution - increase the limit (max 65535) and decrease the TTL of 4-5 minutes to 1 minute. |
Podge.
The Hunger Site - Click to donate free food | My Blog | Snitz 3.4.05 AutoInstall (Beta!)
My Mods: CAPTCHA Mod | GateKeeper Mod
Tutorial: Enable subscriptions on your board
Warning: The post above or below may contain nuts. |
Edited by - Podge on 20 November 2004 08:28:07 |
|
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 08:31:27
|
| That might help, but at the moment I'm using Access. If Gremlin agrees, he will apply the changes and see if there's any improvement. |
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 08:57:31
|
Yes, Gremlin has this set to a fairly low value, but for the users that use active.asp it's the pits! ... if you cross over the restart time then you're "last visited" date gets reset ... not fun at all.
But we are working towards a solution asap. |
|
|
|
Podge
Support Moderator
Ireland
3775 Posts |
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 20 November 2004 : 11:12:04
|
quote:
All these objects are not closed :
admin_config_order.asp : rsCount
admin_count.asp : Server2, or can we close it ?
admin_forums.asp : Server2, drs, delRep, rsTcheck
admin_login.asp : dbRs not (now that IS used a lot)
admin_login_short.asp : dbRs
admin_moderators.asp : rs
admin_mod_dbsetup.asp : objFile, objFolder, objFolderContents
inc_func_common.asp : strNTUserInfo
inc_mail.asp : iConf, Flds, gMDUser, gMDMessageInfo
pop_lock.asp : rs
pop_moderate.asp : rsSub
Now this is the "extra info" I was talking about. These MIGHT be related to MODs, but I'm concerned about the Server2 objects. I know it was added to get around a Brinkster hangup but that could be causing a larger issue
I don't know how many times I am going to have to say this, but the only one of these that may be a problem is the mail stuff. unless you use all those admin pages hundreds of times a day, which I very much doubt. strNTUserInfo is only if you are using NT authentication, which I doubt too, since you are running a website not an intranet.
pop lock is only used when you lock a topic, so once again is very unlikely to be a problem unless you are locking/unlocking hundreds of posts at a time. Also, you will not be using all the objects in inc_mail, depends what your using for your mail. |
|
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 17:39:34
|
| Huw, please re-read my first post. I'm trying to highlight problems with the base code REGARDLESS of my current forum problem. I thought I was being proactive in highlighting these problems, but it feels like not. Please completely disregard my forum problem and look at the fixing the coding issues I have highlighted. |
|
|
|
HuwR
Forum Admin
United Kingdom
20584 Posts |
Posted - 20 November 2004 : 19:13:44
|
| I have already explained several times why these should not be considered "problems" |
|
|
|
Tam
New Member
Sweden
56 Posts |
Posted - 20 November 2004 : 19:36:03
|
| If they aren't closed in basecode, why not just say "Ok, we will make sure they are closed in next release", even if they wouldn't cause trouble if left open. |
|
|
|
MarkJH
Senior Member
United Kingdom
1722 Posts |
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 20 November 2004 : 19:52:33
|
quote:
Originally posted by HuwR
I have already explained several times why these should not be considered "problems"
So the "concerns" I am posting are obviously insignificant compared to the other "problems" posted where the </a> and </font> are in the wrong order and should really be </font> then </a>
quote:
I would think you of all people Huw wouldn't be recommending to someone bad coding practices.
My whole point in raising this thread, but I might just fix all the problems myself and not worry about alerting others to basecode problems. |
|
|
|
Topic |
|
Topic Locked
