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:
How to Display text in empty fields (1997)
[NT] ie 4.0 required (1997)
OT: Unix Geek Needed (2005)
[WebDNA] Searching for encrypted values (2014)
Which beta for w* 4.1 and a problem w/b12 (1999)
User / Pass in TCP connect (2007)
Modtime bug? (2002)
$purchase WITHOUT creditcar (1997)
Custom WebCat Prefs ... (1997)
Credit Card Checksum (1997)
Internet Explorer 6 Form problems (2005)
Post arguments problem mac? (1997)
Document Contains No Data! (1997)
WC2.0 Memory Requirements (1997)
BannerAds demo (1998)
Support ?? (1997)
Date search bug (1997)
[OT] Theiving B*****ds (2004)
Ok here is a question? (1997)
[WebDNA] Was there ever a BeOS compatible version? (2009)