Re: anyone using Webcat 4.x in production?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 36171
interpreted = N
texte = pretty well but there were a lot of adjustments. i have not experienced these particular problems. I am running on red hat linux 6.2 and 4.0 webcat.we have had the:sticky template cache poblems. (This is the worst - makes updating sites very dificult - and why should we need to add randoms etc to links?) it is imposible for the end user to figure out. -- 4.02 supposidly fixes this i cant wait to try.the 1 meg html limit problem. -- 4.02 fixes thisthe no spaces in fields issue (one database supplied by a client)i have found several other problems in development that others had noted and worked around as i neded to.:format command when applied to a longer number than the number of places that you wish to format to [format thousands .6d] 1234567890 [/format] brings absolutely wierd results and as such was useless as i tries to find the largest number in a sequence. also it is unfortunate you cannot get rid of the commas.(without a character replace)when passing variables by redirect you must use [interpret] and [raw] to format the variables in the url prior to the redirect or they truncate.the option for [GETMIMEHEADER ] for name^'host' does not work so that there needs to be two versions written - one for linux with 'host' and one for NT with 'HTTP-HOST'random sort does not work.le does not work it is actually equivelent to less than.not part of webcat but--(cookies in Netscape-suck since the latest does not overwrite the oldest the oldest is always first in the list.)Thats it.... jymDale LaFountain wrote:> 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 LaFountain > Vice President of Information Technology, WebMaster > Dark Horse Comics, Inc. mailto:dalel@darkhorse.com > Phone: 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 -- Affordable - Powerful - Internet Jym Duane -President - CyberLive, Inc. Phone: (949) 443-1323 Fax: (949)443-1360 Email: sales@cyberlive.com Web: http://www.cyberlive.com 34700 Pacific Coast Highway, Suite 306, Capistrano Beach, CA 92624############################################################# 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:

    
  1. Re: anyone using Webcat 4.x in production? (John Butler 2000)
  2. Re: anyone using Webcat 4.x in production? (Jym Duane 2000)
  3. Re: anyone using Webcat 4.x in production? (Jym Duane 2000)
  4. Re: anyone using Webcat 4.x in production? (Jym Duane 2000)
  5. Re: anyone using Webcat 4.x in production? (John Peacock 2000)
  6. Re: anyone using Webcat 4.x in production? (Jym Duane 2000)
  7. anyone using Webcat 4.x in production? (Dale LaFountain 2000)
pretty well but there were a lot of adjustments. i have not experienced these particular problems. I am running on red hat linux 6.2 and 4.0 webcat.we have had the:sticky template cache poblems. (This is the worst - makes updating sites very dificult - and why should we need to add randoms etc to links?) it is imposible for the end user to figure out. -- 4.02 supposidly fixes this i cant wait to try.the 1 meg html limit problem. -- 4.02 fixes thisthe no spaces in fields issue (one database supplied by a client)i have found several other problems in development that others had noted and worked around as i neded to.:format command when applied to a longer number than the number of places that you wish to format to [format thousands .6d] 1234567890 [/format] brings absolutely wierd results and as such was useless as i tries to find the largest number in a sequence. also it is unfortunate you cannot get rid of the commas.(without a character replace)when passing variables by redirect you must use [interpret] and [raw] to format the variables in the url prior to the redirect or they truncate.the option for [GETMIMEHEADER ] for name^'host' does not work so that there needs to be two versions written - one for linux with 'host' and one for NT with 'HTTP-HOST'random sort does not work.le does not work it is actually equivelent to less than.not part of webcat but--(cookies in Netscape-suck since the latest does not overwrite the oldest the oldest is always first in the list.)Thats it.... jymDale LaFountain wrote:> 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 LaFountain > Vice President of Information Technology, WebMaster > Dark Horse Comics, Inc. mailto:dalel@darkhorse.com > Phone: 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 -- Affordable - Powerful - Internet Jym Duane -President - CyberLive, Inc. Phone: (949) 443-1323 Fax: (949)443-1360 Email: sales@cyberlive.com Web: http://www.cyberlive.com 34700 Pacific Coast Highway, Suite 306, Capistrano Beach, CA 92624############################################################# 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 Jym Duane

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:

Emailer on NT! (1998) Re:quit command on NT (1997) Bug Report, maybe (1997) action=add works with IE but not Communicator (2000) Change to 5.0 per website licensing (2003) Date Formats (1997) Mass Mail (2000) WebDNA Book? (2003) Server IP Address (2003) Re:Emailer and encryption (1997) Navigator 4.01 (1997) Interfacing WebMerchant to www.fedex.com (1997) Re:multiple digests, please stop (1997) Uploading very large image files (2003) WebCat2 - Getting to the browser's username/password data (1997) Problem displaying search result (1997) NumFound (1999) WebCatalog Technical Reference (1997) Summing fields (1997) [OT] JS snippet needed (2006)