Re: [WebDNA] Re: WebDNA7 site randomly dropping tags
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107636
interpreted = N
texte = I ran a search and deleted every WebDNA instance except one. Problem = solved, I'll go from here then. Thanks for the help On Nov 2, 2011, at 3:03 PM, christophe.billiottet@webdna.us wrote: > OK, maybe you are running several copies of WebDNA and they all try to = access the same db, with conflicts. >=20 > try to add this in your config: >=20 > DefaultMaxClassProcessCount 1 >=20 >=20 > This states that only one engine can run per web server instance.=20 > Without this, you could have corruption to db files, since they are = stored within memory of the FastDNA engine. > WebDNA spawns its own threads, and maintains the db within memory. If = you have more than one process of FastDNA accessing the same DB files, = they will collide, since they don't share the db in the same memory. >=20 > This could explain what you are seeing now. >=20 >=20 > - chris >=20 >=20 >=20 > On Nov 2, 2011, at 16:48, aaronmichaelmusic@gmail.com wrote: >=20 >> wow, I just ran this test again with another variation. When I = refresh the found items page, I am seeing the results bounce between 3 = different sets of records now. >> Its like multiple instances of the db are being cached and the search = doesn't know which one to get, so it picks one at random. =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 >> --------------------------------------------------------- >> 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
Associated Messages, from the most recent to the oldest:
I ran a search and deleted every WebDNA instance except one. Problem = solved, I'll go from here then. Thanks for the help On Nov 2, 2011, at 3:03 PM, christophe.billiottet@webdna.us wrote: > OK, maybe you are running several copies of WebDNA and they all try to = access the same db, with conflicts. >=20 > try to add this in your config: >=20 > DefaultMaxClassProcessCount 1 >=20 >=20 > This states that only one engine can run per web server instance.=20 > Without this, you could have corruption to db files, since they are = stored within memory of the FastDNA engine. > WebDNA spawns its own threads, and maintains the db within memory. If = you have more than one process of FastDNA accessing the same DB files, = they will collide, since they don't share the db in the same memory. >=20 > This could explain what you are seeing now. >=20 >=20 > - chris >=20 >=20 >=20 > On Nov 2, 2011, at 16:48, aaronmichaelmusic@gmail.com wrote: >=20 >> wow, I just ran this test again with another variation. When I = refresh the found items page, I am seeing the results bounce between 3 = different sets of records now. >> Its like multiple instances of the db are being cached and the search = doesn't know which one to get, so it picks one at random. =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 >> --------------------------------------------------------- >> 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
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:
access denied problem (1997)
Can I invoke an ssi plugin from within a webcat page (1997)
[WriteFile] problems (1997)
Looking for WebDNA 3.08 MAC (2003)
Multiple Web Delivery Methods?? (1999)
redirect strangeness (2000)
[WebDNA] Database Error -oRiGiNaL- (2012)
[switch] platform specific bug??? (2003)
file browser. (2002)
Searching (second post) (1999)
QuitFeedback & DBNotOpened errors (1997)
[Way OT] Workstation Security (2002)
WebCat2.0 [format thousands .0f] no go (1997)
[protect admin] (1997)
PCS search results page (1998)
Zip Code Radius Search Tool (2003)
international time (1997)
Users and groups for local directories (1999)
Sample Tearoom Search Error (1997)
math on date? (1997)