Re: [WebDNA] Re: WebDNA7 site randomly dropping tags
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107635
interpreted = N
texte = Damn. the close- and flush- dbs commands actually don't work with this =test. The strange behavior doesn't stop until I restart apacheBTW, I'm not getting any errors in the Apache logsOn Nov 2, 2011, at 2:42 PM, aaronmichaelmusic@gmail.com wrote:> Chris, I uploaded your page and ran it. I then created another page =(stress3.dna) that only did the search and found items>=20> After running stress2.dna once, I quickly changed your append string =from ftzn[index]ftzn to qwer[index]qwer> Then I ran stress2.dna again> Next I opened up stress3.dna.>=20> At first I saw what I should..a bunch of records beginning with qwer>=20> After a couple refreshes, all of the records began with ftzn. With =continuous refreshing of stress3.dna, I would see the displayed records =bounce back and forth between the actual disk records and the records of =the previous append loop. The db (speed.db) is exactly as it should be.>=20>=20>=20> On Nov 2, 2011, at 2:24 PM, christophe.billiottet@webdna.us wrote:>=20>> Just setup a small test: this adds 10,000 records to a small database =and immediately read them in the same file: it is instantaneous on my =WebDNA 7 test server.>>=20>>
>>=20>> - chris>>=20>> On Nov 2, 2011, at 13:38, aaronmichaelmusic@gmail.com wrote:>>=20>>> After spending a lot of time with apache configurations, I'm =convinced it is WebDNA and not my configuration.>>>=20>>> I am down to just one site running now with a clean configuration. =I still get the 'bouncing' database behavior between the actual and =previously cached versions throughout refreshes.>>>=20>>> To illustrate whats going on=85.>>>=20>>> Say I have a screen listing database records and I have a GUI to add =new ones, and I quickly add 3 new ones>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>> new1>>> new2>>> new3>>>=20>>>=20>>> after a couple refreshes, I get this>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>>=20>>>=20>>> and even more peculiar, I might get this>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>> new2>>>=20>>>=20>>> I've been able to reproduce this behavior over and over again and =with deleting or modifying records as well.>>>=20>>> If I leave it alone for a few minutes and come back, it seems like =it corrected itself and displays the correct records consistently. =Also, manually flushing the databases works too.>>>=20>>> This is really bizarre, and quite frustrating as well. =20>>>=20>>>=20>>>=20>>>=20>>>=20>>> On Nov 1, 2011, at 5:23 PM, christophe.billiottet@webdna.us wrote:>>>=20>>>>=20>>>> On Nov 1, 2011, at 19:08, aaronmichaelmusic@gmail.com wrote:>>>>=20>>>>>>=20>>>>>> note this configuration is already out of the WebDNA scope: you =should add one WebDNA.fcgi copy per website.>>>>> I'm using one copy per site, but I copied and pasted the entire =directory (with .fcgi file and all) to another. =20>>>>=20>>>> and did you setup httpd.conf accordingly? for instance (just an =example) for an OSX server>>>> you would just have to add one line for each new site to the main =httpd.conf block:>>>>=20>>>> >>>> FastCGIServer =/Library/WebServer/Documents/testosx1.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> Action webdna-fastcgi /WebDNA/WebDNA.fcgi>>>> AddHandler webdna-fastcgi .dna>>>> FastCGIServer =/Library/WebServer/Documents/testosx2.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> >>>>=20>>>>=20>>>> And if you had a 3rd one, you'd add:>>>> FastCGIServer =/Library/WebServer/Documents/testosx3.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> and so forth.>>>>=20>>>> Otherwise, a single copy of WebDNA.fcgi is handling all your =websites...>>>>=20>>>>=20>>>> - chris--------------------------------------------------------->>>> This message is sent to you because you are subscribed to>>>> the mailing list .>>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us>>>> Bug Reporting: support@webdna.us>>>=20>>> --------------------------------------------------------->>> This message is sent to you because you are subscribed to>>> the mailing list .>>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us>>> Bug Reporting: support@webdna.us>>=20>=20
Associated Messages, from the most recent to the oldest:
Damn. the close- and flush- dbs commands actually don't work with this =test. The strange behavior doesn't stop until I restart apacheBTW, I'm not getting any errors in the Apache logsOn Nov 2, 2011, at 2:42 PM, aaronmichaelmusic@gmail.com wrote:> Chris, I uploaded your page and ran it. I then created another page =(stress3.dna) that only did the search and found items>=20> After running stress2.dna once, I quickly changed your append string =from ftzn[index]ftzn to qwer[index]qwer> Then I ran stress2.dna again> Next I opened up stress3.dna.>=20> At first I saw what I should..a bunch of records beginning with qwer>=20> After a couple refreshes, all of the records began with ftzn. With =continuous refreshing of stress3.dna, I would see the displayed records =bounce back and forth between the actual disk records and the records of =the previous append loop. The db (speed.db) is exactly as it should be.>=20>=20>=20> On Nov 2, 2011, at 2:24 PM, christophe.billiottet@webdna.us wrote:>=20>> Just setup a small test: this adds 10,000 records to a small database =and immediately read them in the same file: it is instantaneous on my =WebDNA 7 test server.>>=20>> >>=20>> - chris>>=20>> On Nov 2, 2011, at 13:38, aaronmichaelmusic@gmail.com wrote:>>=20>>> After spending a lot of time with apache configurations, I'm =convinced it is WebDNA and not my configuration.>>>=20>>> I am down to just one site running now with a clean configuration. =I still get the 'bouncing' database behavior between the actual and =previously cached versions throughout refreshes.>>>=20>>> To illustrate whats going on=85.>>>=20>>> Say I have a screen listing database records and I have a GUI to add =new ones, and I quickly add 3 new ones>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>> new1>>> new2>>> new3>>>=20>>>=20>>> after a couple refreshes, I get this>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>>=20>>>=20>>> and even more peculiar, I might get this>>>=20>>> records>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>>> old1>>> old2>>> old3>>> new2>>>=20>>>=20>>> I've been able to reproduce this behavior over and over again and =with deleting or modifying records as well.>>>=20>>> If I leave it alone for a few minutes and come back, it seems like =it corrected itself and displays the correct records consistently. =Also, manually flushing the databases works too.>>>=20>>> This is really bizarre, and quite frustrating as well. =20>>>=20>>>=20>>>=20>>>=20>>>=20>>> On Nov 1, 2011, at 5:23 PM, christophe.billiottet@webdna.us wrote:>>>=20>>>>=20>>>> On Nov 1, 2011, at 19:08, aaronmichaelmusic@gmail.com wrote:>>>>=20>>>>>>=20>>>>>> note this configuration is already out of the WebDNA scope: you =should add one WebDNA.fcgi copy per website.>>>>> I'm using one copy per site, but I copied and pasted the entire =directory (with .fcgi file and all) to another. =20>>>>=20>>>> and did you setup httpd.conf accordingly? for instance (just an =example) for an OSX server>>>> you would just have to add one line for each new site to the main =httpd.conf block:>>>>=20>>>> >>>> FastCGIServer =/Library/WebServer/Documents/testosx1.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> Action webdna-fastcgi /WebDNA/WebDNA.fcgi>>>> AddHandler webdna-fastcgi .dna>>>> FastCGIServer =/Library/WebServer/Documents/testosx2.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> >>>>=20>>>>=20>>>> And if you had a 3rd one, you'd add:>>>> FastCGIServer =/Library/WebServer/Documents/testosx3.domain.net/WebDNA/WebDNA.fcgi =-idle-timeout 60 -processes 1>>>> and so forth.>>>>=20>>>> Otherwise, a single copy of WebDNA.fcgi is handling all your =websites...>>>>=20>>>>=20>>>> - chris--------------------------------------------------------->>>> This message is sent to you because you are subscribed to>>>> the mailing list .>>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us>>>> Bug Reporting: support@webdna.us>>>=20>>> --------------------------------------------------------->>> This message is sent to you because you are subscribed to>>> the mailing list .>>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us>>> Bug Reporting: support@webdna.us>>=20>=20
aaronmichaelmusic@gmail.com
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:
Re:2nd WebCatalog2 Feature Request (1996)
[searh] or [shownext]problem (1998)
Would [arrayset] Work Here? (2005)
TCPConnect to query for Domain expiration (2000)
OT-test (1998)
Execute Applescript (1997)
New Command prefs ... (1997)
frames & carts (1997)
Deleting Orders (1997)
Orderfile Question (2003)
problem (1998)
how do I delete 1 of 2 identical records? (2003)
return missing item (was:WebCat Sales) (1997)
Search for dates greater than [date] (1997)
cookies and [returnraw] (1997)
Problem (1997)
Requiring that certain fields be completed (1997)
[WebDNA] WebDNA and Coda 2 - Get it up and running... (macOS) (2018)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)
WebCat2 Append problem (B14Macacgi) (1997)