anyone using Webcat 4.x in production?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 36163
interpreted = N
texte = Hi webcats,Is anyone else out there running Webcat 4.x on their production server yet? If so, how well is it working for you?We have made a couple runs at upgrading, but have been forced to revert to 3.0.8 every time due to various problems (we're running Webstar 4.2, OS9.0.4 on a 256MB G4/500 with 160MB allocated to webstar). Webcatalog 4.x (4.0.2b6 most recently) works just great on a development server, but as soon as it's hit with a production-load of requests (30,000+ page requests/day) webcatalog will do several Bad Things(tm):- sporadically serve pages very slowly, often to the point that Powerkey thinks webstar is dead and reboots it (>60 sec response for over 5 minutes). If given enough time running at an extremely slow serving speeds (2-10 minutes), webstar often recovers from maxed out connections and begins serving normally again.- sporadically forget where databases are located. Reloading the same page always gets rid of the problem, but it happens quite often on busy databases (like a banners.db that is incremented on every page request).- sporadically neglect to replace or append information to a specified database, likely because the database could not be found on that particular request or sub-request. I have seen the banners.db not found three times on a single page (3 db not found errors displayed), and then have the template find banners.db correctly below in the same request.- bog down the server machine so much that I can't open a Timbuktu control session or Webstar Admin session (quitting and restarting Webstar fixes both of these problems). I have tried moving the cgi-friendlyness slider halfway to CGI in the webstar admin, but that doesn't seem to make any difference here.- eventually become so slow as to need rebooting or Powerkey resets the box within 5,000-50,000 hits. We have never gotten beyond 60,000 hits since upgrading to webcat 4.I'm just curious if anyone else is seeing these kinds of problems with Webcat 4 and the newest beta(s). 4.0.2 is a vast improvement over 4.0 and 4.0.1, but it's still not a usable product for us.I appreciate the time that SMSI has dedicated to the problems we (and others) have reported, but I was hoping for a little more prompt attention to these issues that amount to a great upgrade for a great product that we (and others?) just can't use... If other customers are having some or all of these problems I mentioned and spoke up about them on this list, perhaps SMSI would see fit to dedicate more resources to resolving them.Thanks,Dale-- Dale LaFountainVice President of Information Technology, WebMasterDark Horse Comics, Inc. mailto:dalel@darkhorse.comPhone: 503-652-8815 x324 http://www.darkhorse.com/#############################################################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 To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
Hi webcats,Is anyone else out there running Webcat 4.x on their production server yet? If so, how well is it working for you?We have made a couple runs at upgrading, but have been forced to revert to 3.0.8 every time due to various problems (we're running Webstar 4.2, OS9.0.4 on a 256MB G4/500 with 160MB allocated to webstar). Webcatalog 4.x (4.0.2b6 most recently) works just great on a development server, but as soon as it's hit with a production-load of requests (30,000+ page requests/day) webcatalog will do several Bad Things(tm):- sporadically serve pages very slowly, often to the point that Powerkey thinks webstar is dead and reboots it (>60 sec response for over 5 minutes). If given enough time running at an extremely slow serving speeds (2-10 minutes), webstar often recovers from maxed out connections and begins serving normally again.- sporadically forget where databases are located. Reloading the same page always gets rid of the problem, but it happens quite often on busy databases (like a banners.db that is incremented on every page request).- sporadically neglect to replace or append information to a specified database, likely because the database could not be found on that particular request or sub-request. I have seen the banners.db not found three times on a single page (3 db not found errors displayed), and then have the template find banners.db correctly below in the same request.- bog down the server machine so much that I can't open a Timbuktu control session or Webstar Admin session (quitting and restarting Webstar fixes both of these problems). I have tried moving the cgi-friendlyness slider halfway to CGI in the webstar admin, but that doesn't seem to make any difference here.- eventually become so slow as to need rebooting or Powerkey resets the box within 5,000-50,000 hits. We have never gotten beyond 60,000 hits since upgrading to webcat 4.I'm just curious if anyone else is seeing these kinds of problems with Webcat 4 and the newest beta(s). 4.0.2 is a vast improvement over 4.0 and 4.0.1, but it's still not a usable product for us.I appreciate the time that SMSI has dedicated to the problems we (and others) have reported, but I was hoping for a little more prompt attention to these issues that amount to a great upgrade for a great product that we (and others?) just can't use... If other customers are having some or all of these problems I mentioned and spoke up about them on this list, perhaps SMSI would see fit to dedicate more resources to resolving them.Thanks,Dale-- Dale LaFountainVice President of Information Technology, WebMasterDark Horse Comics, Inc. mailto:dalel@darkhorse.comPhone: 503-652-8815 x324 http://www.darkhorse.com/#############################################################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 To switch to the INDEX mode, E-mail to Send administrative queries to
Dale LaFountain
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:
b12 cannot limit records returned and more. (1997)
Forms Search Questions (1997)
Simple way to create unique SKU (1997)
[OT] Half completed orders (2005)
SKU lookup (1997)
Search all Fields in a db (1997)
Linux WebDNA Server probs (2004)
Security Question (1997)
WC2b15 File Corruption (1997)
Some Questions (1997)
[OT] Indexing of dynamic web sites (2003)
limit to listwords (2001)
Setting up shop (1997)
If Empty ? (1997)
WebCatalog for guestbook ? (1997)
Lots of bounce errors (2007)
WebDNA implementation of MD5 algorithm? (2003)
Time Display from Database (1997)
WebCat2 - Getting to the browser's username/password data (1997)
Browser Check for WebDNA compatability (1999)