Re: Strange intermittent WebDNA problems
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 70084
interpreted = N
texte = OK, I have held back on this idea because there was little to support it, but the sudden increase in occurrences and the repetitive and sometimes simultaneous occurrences may lend some credibility to the idea.... I know that the WebDNA system phones home to report serial number usages. I do not know any details about how and when it does so, just that it does. I am wondering if a failure to respond from SMSI isn't inherently causing some usability issue here. It's entirely possible that the method by which the system reports the usage to SMSI is causing some type of hung process, or cascading failure in 'offending' server. Now, what I don't know, is what type of connection is being made, what type of response the license server expects and what type of return response the customer servers expect. At the risk of sounding paranoid I think that coincidental failures across many many machines with different webservers and OS configurations, coupled with a company that has seemingly abandoned the product could easily point to innocent enough action (we don't need to track serials anymore -- turn that thing off) action on SMSI's part. Am I out in left field here? Alex On 4/9/08 10:43 AM, "Steve Craig"
wrote: > Between myself and a friend who is not on the list, we have 2 WebDNA > machines and they virtually always go off within an hour of each > other. I have never coded anything on his and he has never coded > anything on mine. There are no common sites whatsoever, in fact we > usually have taken very different ways to solve coding things in the > past. So basically no connection other than existing in the same > physical rack. We use the same supplier for access but are on > different subnets. >> I think I'll defer to Steve Craig's assessment and just blame it >> on SMSI attacking our servers! ;-) -- Alex J. McCombie > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > Adventure Skies Interactive > Box 124 Martville, NY 13111 > p. 315 .233 .9403 > e. Alex@AdventureSkies.com > www.AdventureSkies.com ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
OK, I have held back on this idea because there was little to support it, but the sudden increase in occurrences and the repetitive and sometimes simultaneous occurrences may lend some credibility to the idea.... I know that the WebDNA system phones home to report serial number usages. I do not know any details about how and when it does so, just that it does. I am wondering if a failure to respond from SMSI isn't inherently causing some usability issue here. It's entirely possible that the method by which the system reports the usage to SMSI is causing some type of hung process, or cascading failure in 'offending' server. Now, what I don't know, is what type of connection is being made, what type of response the license server expects and what type of return response the customer servers expect. At the risk of sounding paranoid I think that coincidental failures across many many machines with different webservers and OS configurations, coupled with a company that has seemingly abandoned the product could easily point to innocent enough action (we don't need to track serials anymore -- turn that thing off) action on SMSI's part. Am I out in left field here? Alex On 4/9/08 10:43 AM, "Steve Craig" wrote: > Between myself and a friend who is not on the list, we have 2 WebDNA > machines and they virtually always go off within an hour of each > other. I have never coded anything on his and he has never coded > anything on mine. There are no common sites whatsoever, in fact we > usually have taken very different ways to solve coding things in the > past. So basically no connection other than existing in the same > physical rack. We use the same supplier for access but are on > different subnets. >> I think I'll defer to Steve Craig's assessment and just blame it >> on SMSI attacking our servers! ;-) -- Alex J. McCombie > . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . > Adventure Skies Interactive > Box 124 Martville, NY 13111 > p. 315 .233 .9403 > e. Alex@AdventureSkies.com > www.AdventureSkies.com ------------------------------------------------------------- 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://webdna.smithmicro.com/
Alex McCombie
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:
OT : Best book for OSX (2002)
Something wrong with this list? (2006)
About WebDNA (2006)
emailer w/F2 (1997)
READFILE command? (1998)
Details of shipping - Totalqty calculations (1997)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
WebDelivery: One step closer !! (1997)
A multi-processor savvy WebCatalog? (1997)
Date Sorting (1997)
textA (1998)
WC Database Format (1997)
Date math (1997)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)
stuck time (1998)
Caching pages...again (2001)
Webcat no longer supported? (2006)
Problems with webcat 2.01 for NT (1997)
UPDATE PROBLEM (1997)
WebCatalog2 Feature Feedback (1996)