Re: [WebDNA] triggers.db "next execute" fails to update

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108350
interpreted = N
texte = Typo in your "Validation Text" ? On 29/01/2012, at 4:29 PM, Kenneth Grome wrote: > I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. > This is the only trigger used in this sandbox. > > When it runs WebDNA fails update the "next execute" value > like it is supposed to. Therefore the trigger runs again > every 10 seconds, and the same template is interpreted by > WebDNA again ... > > This is a "bad thing" when the template has a sendmail > context it it to alert me that the trigger has run, because > it sends me another email every 10 seconds. I got more than > 1500 emails this morning before the host put an end to it by > rebooting the server ... :( > > Flushing the databases does not stop the trigger from > running. Deleting the target template via FTP does not stop > it, because even though the file is no longer on disk it is > apparently still cached in RAM. Strangely enough, the > template seems to remain cached in RAM , thus ignoring the > WebCatalog Prefs that's supposed to force the template out > of ram every 2 seconds. Issuing a FlushCache command also > fails to purge the template from RAM. > > :( > > My host refuses to investigate this issue. Whether he is > lazy, irresponsible, incompetent, or all of the above, > cannot say for certain. Nevertheless I need the problem > fixed, so I'll have to figure this out myself, hopefully with > some bright ideas from others here. > > Any idea why WebDNA might fail to update the "next execute" > value when the trigger is run? > > Sincerely, > Kenneth Grome > --------------------------------------------------------- > 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:

    
  1. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  2. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
  3. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  4. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
  5. [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  6. Re: [WebDNA] triggers.db "next execute" fails to update (Stuart Tremain 2012)
  7. Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  8. [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Donovan Brooke 2012)
  9. Re: [WebDNA] triggers.db "next execute" fails to update (sal danna 2012)
  10. Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  11. Re: [WebDNA] triggers.db "next execute" fails to update (Rob 2012)
  12. Re: [WebDNA] triggers.db "next execute" fails to update (Govinda 2012)
  13. Re: [WebDNA] triggers.db "next execute" fails to update (William DeVaul 2012)
  14. [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
Typo in your "Validation Text" ? On 29/01/2012, at 4:29 PM, Kenneth Grome wrote: > I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. > This is the only trigger used in this sandbox. > > When it runs WebDNA fails update the "next execute" value > like it is supposed to. Therefore the trigger runs again > every 10 seconds, and the same template is interpreted by > WebDNA again ... > > This is a "bad thing" when the template has a sendmail > context it it to alert me that the trigger has run, because > it sends me another email every 10 seconds. I got more than > 1500 emails this morning before the host put an end to it by > rebooting the server ... :( > > Flushing the databases does not stop the trigger from > running. Deleting the target template via FTP does not stop > it, because even though the file is no longer on disk it is > apparently still cached in RAM. Strangely enough, the > template seems to remain cached in RAM , thus ignoring the > WebCatalog Prefs that's supposed to force the template out > of ram every 2 seconds. Issuing a FlushCache command also > fails to purge the template from RAM. > > :( > > My host refuses to investigate this issue. Whether he is > lazy, irresponsible, incompetent, or all of the above, > cannot say for certain. Nevertheless I need the problem > fixed, so I'll have to figure this out myself, hopefully with > some bright ideas from others here. > > Any idea why WebDNA might fail to update the "next execute" > value when the trigger is run? > > Sincerely, > Kenneth Grome > --------------------------------------------------------- > 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 Stuart Tremain

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:

Location of Browser Info.txt file (1997) Database changes (1998) Loops N Variables (1998) Trouble with formula.db (1997) Great product and great job ! (1997) RE: WebDNA-Talk searchable? (1997) IIS4b2 and WebCatalog b19 (1997) WebCat2 beta 11 - new prefs ... (1997) too many nested [xxx] (1997) WriteFile is there a max size? (1998) WCS Newbie question (1997) Banner Ad example (Typhoon) and WebCatalog (1997) Summing fields (1997) [OT] Communigate List (2003) RE: Discounting prices across a site (1997) error (2000) Site Specific Shopping Cart folder and Orderfiles (2000) [search] in formulas.db (1997) contextual shownext (1998) Document Contains No Data! (1997)