Re: RAM issue

This WebDNA talk-list message is from

2006

It keeps the original formatting. numero = 67659
interpreted = N
texte = Yes server admin found nothing out of the ordinary. However we did find the problem, and yes it was not related to RAM. Its was due to a bug in webdna's [TABLE] context.When we use the [table] context the memory used for the [table] is not removed from our server's RAM. Instead it simply accumulates until the server runs out and DBSever.exe crashes. The page still stays up, but dbs don't work because available memory is used up, therefore the server generates tons of 'Not enough memory errors....' and no one can use the site.We previously suspected that [table] was not stable, but this proved it for us. The server crashed every day last week, today we removed the code snippet and all is fine, memory stabilized. We had discovered that every time this page was loading, this small [table] containing three records, was not being removed from the server RAM like a normal .db.Another member to add to WebDNA errata.-adamBess Ho wrote:> It concerns me too. Did you have experience network admin to check out your web server? to see if you have to do some server maintainance such as defrag etc?>> I am thinking your webdna server crash is caused by another incident unrelated to RAM?>> -----Original Message-----> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of> Adam O'Connor> Sent: Wednesday, June 28, 2006 12:55 PM> To: WebDNA Talk> Subject: RAM issue>>> Quick question, I am working with a Win2003 webdna server which had 2g > of RAM, then was upgraded to 4g RAM. However only 1,003,388 is shown as > being used by webcat. At some points the server is crashing because > webcat is complaining of not having enough memory, but never goes above > 700meg. What's the deal? Do I have to reinstall webcat? Is it a > registry issue on the sever? Am I missing a config issue regarding webcat?>> Anyone experience this before?>> -Adam>> -------------------------------------------------------------> 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 > Web Archive of this list is at: http://webdna.smithmicro.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 > Web Archive of this list is at: http://webdna.smithmicro.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 Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: RAM issue ( "Bess Ho" 2006)
Re: RAM issue ( Adam O'Connor 2006)
Re: RAM issue ( Chris 2006)
Re: RAM issue ( Adam O'Connor 2006)
Re: RAM issue ( "Bess Ho" 2006)
Re: RAM issue ( "Nitai @ ComputerOil" 2006)
RAM issue ( Adam O'Connor 2006)

Yes server admin found nothing out of the ordinary. However we did find the problem, and yes it was not related to RAM. Its was due to a bug in webdna's [table] context.When we use the [table] context the memory used for the [table] is not removed from our server's RAM. Instead it simply accumulates until the server runs out and DBSever.exe crashes. The page still stays up, but dbs don't work because available memory is used up, therefore the server generates tons of 'Not enough memory errors....' and no one can use the site.We previously suspected that [table] was not stable, but this proved it for us. The server crashed every day last week, today we removed the code snippet and all is fine, memory stabilized. We had discovered that every time this page was loading, this small [table] containing three records, was not being removed from the server RAM like a normal .db.Another member to add to WebDNA errata.-adamBess Ho wrote:> It concerns me too. Did you have experience network admin to check out your web server? to see if you have to do some server maintainance such as defrag etc?>> I am thinking your webdna server crash is caused by another incident unrelated to RAM?>> -----Original Message-----> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of> Adam O'Connor> Sent: Wednesday, June 28, 2006 12:55 PM> To: WebDNA Talk> Subject: RAM issue>>> Quick question, I am working with a Win2003 webdna server which had 2g > of RAM, then was upgraded to 4g RAM. However only 1,003,388 is shown as > being used by webcat. At some points the server is crashing because > webcat is complaining of not having enough memory, but never goes above > 700meg. What's the deal? Do I have to reinstall webcat? Is it a > registry issue on the sever? Am I missing a config issue regarding webcat?>> Anyone experience this before?>> -Adam>> -------------------------------------------------------------> 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 > Web Archive of this list is at: http://webdna.smithmicro.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 > Web Archive of this list is at: http://webdna.smithmicro.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 Web Archive of this list is at: http://webdna.smithmicro.com/ Adam O'Connor

DOWNLOAD WEBDNA NOW!

Re: RAM issue

2006

Top Articles:

Related Readings: