Re: Which beta for w* 4.1 and a problem w/b12

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 25427
interpreted = N
texte = At 2:13 AM 12/13/99, Grant Hulbert wrote: >> >I will load up the dev server and try and reproduce, but what is it you >> >would want? The returned html? The w* debug logs? >> >> I'm hoping for a sequence that will reproduce the behavior so I can >> do it here on one of my machines. And perhaps a copy of the returned >> HTML would help, in case we can see some interesting data in it that >> would provide a clue. >>I tried unsuccessfully last night to get b12 to reproduce the error. The munged html may have been a hiccup. The problem is that there's no way I can simulate 5,000 database browsers (users) a day all working on my site on the development server. And I can't risk running b12 on the live server unless I'm watching it like a hawk. And I'm basically a one-person shop (as far as the web site goes) and I'm too busy with developing new required features for the site that are due Wednesday to keep an eye on the live server for experiements.So the summary is: -3.0.4 and w*4.1 seems to crash with error type 2 and error type 12 and w* quits without a crash and writes heapmanager errors to the w*messages log. These heap manager errors appear to eventually cause w* to quit. Starnine's solution: upgrade to 4.1All the 3.0.5 betas seems to run without crashing and without heap manager errors except: -3.0.5b12 I had the case of munged html. -3.0.5b11 has the exiration header issue. -3.0.5b10 seems to have a different expiration date issue.Anyone else besides me running 3.0.5 betas with w* 4.1 and if so, what are your experiences?___Joe____________________________________________________ Joseph D'Andrea JoeDan@West21.com WEST21.com Internet services for the 21st Century http://www.west21.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:

    
  1. Re: Which beta for w* 4.1 and a problem w/b12 (Grant Hulbert 1999)
  2. Re: Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
  3. Re: Which beta for w* 4.1 and a problem w/b12 (Grant Hulbert 1999)
  4. Re: Which beta for w* 4.1 and a problem w/b12 (Conrad Hubbard 1999)
  5. Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
  6. Re: Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
  7. Re: Which beta for w* 4.1 and a problem w/b12 (Grant Hulbert 1999)
  8. Re: Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
  9. Re: Which beta for w* 4.1 and a problem w/b12 (Grant Hulbert 1999)
  10. ADDEMDUM: Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
  11. Which beta for w* 4.1 and a problem w/b12 (Joseph D'Andrea 1999)
At 2:13 AM 12/13/99, Grant Hulbert wrote: >> >I will load up the dev server and try and reproduce, but what is it you >> >would want? The returned html? The w* debug logs? >> >> I'm hoping for a sequence that will reproduce the behavior so I can >> do it here on one of my machines. And perhaps a copy of the returned >> HTML would help, in case we can see some interesting data in it that >> would provide a clue. >>I tried unsuccessfully last night to get b12 to reproduce the error. The munged html may have been a hiccup. The problem is that there's no way I can simulate 5,000 database browsers (users) a day all working on my site on the development server. And I can't risk running b12 on the live server unless I'm watching it like a hawk. And I'm basically a one-person shop (as far as the web site goes) and I'm too busy with developing new required features for the site that are due Wednesday to keep an eye on the live server for experiements.So the summary is: -3.0.4 and w*4.1 seems to crash with error type 2 and error type 12 and w* quits without a crash and writes heapmanager errors to the w*messages log. These heap manager errors appear to eventually cause w* to quit. Starnine's solution: upgrade to 4.1All the 3.0.5 betas seems to run without crashing and without heap manager errors except: -3.0.5b12 I had the case of munged html. -3.0.5b11 has the exiration header issue. -3.0.5b10 seems to have a different expiration date issue.Anyone else besides me running 3.0.5 betas with w* 4.1 and if so, what are your experiences?___Joe____________________________________________________ Joseph D'Andrea JoeDan@West21.com WEST21.com Internet services for the 21st Century http://www.west21.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 Joseph D'Andrea

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:

problems with 2 tags (1997) DON'T use old cart file! (1997) [HIDEIF] inside [FOUNDITEM] (1997) Stopping bad HTML propagation ? (1997) Linux [decrypt] bug exists only on webcat 3 or also 4? (2000) Odd error in logs (1998) Question re: FlushDatabases (1997) [isfile] ? (1997) Hosts who have upgraded to v5.0? (2003) Roundup function? (1997) [isfile] ? (1997) Problems reading files created by WC (1997) Add to Cart & List of Products (1997) Anyone with a solution for this? (2001) [OT] Connect to MySQL (2004) searchable list archive (1997) Date Math (1999) Cart date/time (2006) Windows-based Code Editor (2002) The word TYPE in search contexts and fields (1998)