Re: WebCat 3.04-3.07 plug-in dying on server....
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 28744
interpreted = N
texte = on 3/8/00 9:31 PM, Bill Heissenbuttel at bill@pagehouse.com wrote:> Ken, > > At 9:34 PM -1000 03/7/00, Kenneth Grome wrote: > >>>> My gut feeling is that you may see >>>> the same problems even after you replace the plugin with the cgi, >>>> thus narrowing things down to either a bug in webcat or a coding >>>> problem in one of your templates >>> >>> It's not going to be a coding problem because it's universal- among >>> 15-20 sites with 5 different developers, so none of the code is all >>> from one shop. >> >> If all the sites are on the same server, then it is very possible -- >> and very likely -- that someone has uploaded a template that is >> killing webcatalog, and thereby killing every webcat site on the >> server. The problem wouldn't show up until someone requests that >> page, and then the bad code kills webcat ... > > Yes, I understand what you're saying, but the code should just kill > WebCat, instead, WebCat does a slow agonizing death over 20-60 > minutes. LIke I mentioned in the original post, WebCat slowly goes > deaf and starts missing bits of code here and there, to the point > where it just stops cold. The time frame has been as long as 2 hours > and as short as 15-20 minutes.This is identical to the problem I posted last week regarding the CGI. We have since upgraded to Web* 4.2 and the plugin version of WebCat 3.0.7. We have actually seen an increase in stability (not just speed) with the plugin. In fact after 3 days not a single deafness. > HEY, SMITH-MICRO! Can I turn on the Technical Support logging and > have you help me weed out the problems? > > Bill I can't wait to hear what you find Bill. We can't afford the TSL option as it slows down performance on a critical server. To repeat, we saw sporadic occurrences where WebCat would exhibit server slowdowns until it finally ended up not serving any WebDNA pages. In fact, one common thing we server is WebCat backended by NetCloak. In those cases, netcloak would eventually return an error saying that the backend cgi (WebCat) did not respond in the allotted time. Since moving to the plugin and Web* 4.2 we have not had the deafness reoccur. (3 days now) where it occurred 5 times during the weekend previous to the upgrade. But..... I did notice a moderate slowdown in WebCat plugin only after 24 hours of continuous use. Quitting WebStar and relaunching it caused a _dramatic_ increase in performance immediately. So we have now resolved to a daily restart to keep performance where we like it.Config. system 8.5 WebStar 4.2 netcloak Plugin siteedit Plugin WebCat Plugin 3.0.7(worse on acgi) WebStar data Cache WebStar ssi WebStar AdminPlenty of Ram (webstar minimum unused memory is at least 10+ megs)ajm-- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
on 3/8/00 9:31 PM, Bill Heissenbuttel at bill@pagehouse.com wrote:> Ken, > > At 9:34 PM -1000 03/7/00, Kenneth Grome wrote: > >>>> My gut feeling is that you may see >>>> the same problems even after you replace the plugin with the cgi, >>>> thus narrowing things down to either a bug in webcat or a coding >>>> problem in one of your templates >>> >>> It's not going to be a coding problem because it's universal- among >>> 15-20 sites with 5 different developers, so none of the code is all >>> from one shop. >> >> If all the sites are on the same server, then it is very possible -- >> and very likely -- that someone has uploaded a template that is >> killing webcatalog, and thereby killing every webcat site on the >> server. The problem wouldn't show up until someone requests that >> page, and then the bad code kills webcat ... > > Yes, I understand what you're saying, but the code should just kill > WebCat, instead, WebCat does a slow agonizing death over 20-60 > minutes. LIke I mentioned in the original post, WebCat slowly goes > deaf and starts missing bits of code here and there, to the point > where it just stops cold. The time frame has been as long as 2 hours > and as short as 15-20 minutes.This is identical to the problem I posted last week regarding the CGI. We have since upgraded to Web* 4.2 and the plugin version of WebCat 3.0.7. We have actually seen an increase in stability (not just speed) with the plugin. In fact after 3 days not a single deafness. > HEY, SMITH-MICRO! Can I turn on the Technical Support logging and > have you help me weed out the problems? > > Bill I can't wait to hear what you find Bill. We can't afford the TSL option as it slows down performance on a critical server. To repeat, we saw sporadic occurrences where WebCat would exhibit server slowdowns until it finally ended up not serving any WebDNA pages. In fact, one common thing we server is WebCat backended by NetCloak. In those cases, netcloak would eventually return an error saying that the backend cgi (WebCat) did not respond in the allotted time. Since moving to the plugin and Web* 4.2 we have not had the deafness reoccur. (3 days now) where it occurred 5 times during the weekend previous to the upgrade. But..... I did notice a moderate slowdown in WebCat plugin only after 24 hours of continuous use. Quitting WebStar and relaunching it caused a _dramatic_ increase in performance immediately. So we have now resolved to a daily restart to keep performance where we like it.Config. system 8.5 WebStar 4.2 netcloak Plugin siteedit Plugin WebCat Plugin 3.0.7(worse on acgi) WebStar data Cache WebStar ssi WebStar AdminPlenty of Ram (webstar minimum unused memory is at least 10+ megs)ajm-- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Alex McCombie
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
show all problem (1997)
One more time (1997)
2 databases (1997)
More questions about serial number dishing (1997)
Price lookup problem - was Cart questions (1997)
[WebDNA] how can i grab the contents of a post? (2011)
Bug or syntax error on my part? (1997)
[searchString] (1997)
NT b19 sends extra MIME headers (1997)
Newbie search question (between two dates) (2001)
[WebDNA] Create a cryptographic Mac key... (2016)
RE: Signal Raised (1997)
Word search (1997)
SiteGuard Admin Feature ? (1997)
Re(2): NT version and O'reily's WebSite (1997)
Multi-User Security on *nix using mod_rewrite (2002)
Online reference (1997)
2.0 Info (1997)
WC2.0 Memory Requirements (1997)
[WebDNA] CICADA (2008)