Re: [Repost] Triggers, again SM???
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35399
interpreted = N
texte = >>deadlocked :WebCatalog:Triggers.db, 62789163 times waiting for write>Paul,I found the following in the archives:>I would turn on Extended Logging in the WebCatalog Prefs to see if the>triggers are executing only at the time they are supposed to, or if>they are running WAAY more often than they should.>A while ago I hit a trigger bug where the URL was accessed upon>creation of the trigger, and any typo in the URL or responsetext>would cause the trigger to execute every second or two instead of on>its schedule. I'm not sure if it was fixed in 3.0.8 or not, but your>problem sounds very similar.>A deadlock occurs when two threads are attempting to write to the>same db. If you're trying to modify your trigger while the above>runaway situation is occurring, it could very easily cause a deadlock.>I would look very closely at your url and response text to make sure>that you're setup correctly. Then look at the WebCatalog.debug file>in the Webstar root for other clues.Good luck,Glenn-------------------------------------------------------------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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>>deadlocked :WebCatalog:triggers.db, 62789163 times waiting for write>Paul,I found the following in the archives:>I would turn on Extended Logging in the WebCatalog Prefs to see if the>triggers are executing only at the time they are supposed to, or if>they are running WAAY more often than they should.>A while ago I hit a trigger bug where the URL was accessed upon>creation of the trigger, and any typo in the URL or responsetext>would cause the trigger to execute every second or two instead of on>its schedule. I'm not sure if it was fixed in 3.0.8 or not, but your>problem sounds very similar.>A deadlock occurs when two threads are attempting to write to the>same db. If you're trying to modify your trigger while the above>runaway situation is occurring, it could very easily cause a deadlock.>I would look very closely at your url and response text to make sure>that you're setup correctly. Then look at the WebCatalog.debug file>in the Webstar root for other clues.Good luck,Glenn-------------------------------------------------------------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://search.smithmicro.com/
Glenn Busbin
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:
Replace command help (1998)
Wrapping text (1998)
Unix line endings (2003)
X Server (1999)
Max Record length restated as maybe bug (1997)
permissions & webcat (1999)
PROBLEM (1997)
Great product and great job ! (1997)
WebCat2: Items xx to xx shown, etc. (1997)
[WebDNA] Cookie behavior (2010)
Size limit for tmpl editor ? (1997)
WebCat B13 Mac CGI -- Frames question (1997)
How did *you* learn Web Catalog? (2000)
[WebDNA] Triggers not working (2014)
[date format] w/in sendmail (1997)
Security Issues and WebCommerce Solution (1997)
Timer Values on [redirect] (1998)
WebCat2b15MacPlugin - [protect] (1997)
pc (1997)
[Lookup] improvment [feature request] (2004)