Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106878
interpreted = N
texte = No, the reason is that the entire architecture is designed around=20 windows systems - there are tons of things running on the server that=20 require windows, we are thoughouly tied into windows. Moving to LInux,=20 would require that so many services be altered into cron-jobs, and so=20 on. Not to mention the remaining software that is running on the system. Now we could get another machine to run just the webserver on, but the=20 way the system is designed/implemented, that would mean I would have to=20 change all places where webdna refers to the servers, yes I realize this=20 is a horrible way it has been done, nevertheless - that is the way it wor= ks. Hence, moving is not an option. FInally, man upstairs would never go for it, and that usually means end=20 of line anyway. -Tommy On 09-07-2011 17:43, Kenneth Grome wrote: >> Moving is simply not an option. > Why not? > > If it's Windows or IIS that's causing the problem (wow, this > would be a surprise, wouldn't it???) moving it to LInux > would be the fastest, cheapest, and most effective solution. > Why don't you try it? Is the reason because you don't know > how to admin a Linux server? > > You said the problem occurs even when the site is not busy, > so surely you could run a test on Linux to confirm or reject > the theory that it's a Windows/IIS problem and not a WebDNA > problem, right? > > >> I guess ill have to resort to the ultimate solution and >> attempt convince the man upstairs to implement a new >> system, in something other than webdna. > Are you suggesting that rebuilding the entire website in > some other software is an option -- even though it would > obviously cost thousands or tens of thousands of dollars -- > yet moving the existing site to a different server (or > properly reconfiguring the server you already have) which > would cost 2-3 order of magnitude less is NOT an option? > > Sorry, but I fail to see any logic in this at all. > > >> I realize it is not a very large DB; it only contains who >> is online, and so on, but what I am still wondering is why >> webdna is not able to write to it. > The answer is more than likely bad WebDNA code by the person > who wrote it (or modified it) or bad server configuration. Do > you have enough experience with WebDNA to be able to > diagnose a potential WebDNA problem? > > I'm willing to bet that WebDNA will work just fine on the > current server -- once you fix the server or the WebDNA code > that is causing this problem. > > >> yes it is doing this, even when there is not heavy load > After more than 16 years of programming WebDNA I have yet to > see a problem like this that I cannot fix -- especially one > where the problem is reportedly NOT due to extremely heavy > traffic on the server! > > >> our visitor >> numbers have dropped significantly, we explain it by the >> myriad of problems we've been having with webdna ... > Maybe these "problems" are caused by a badly configured IIS > server that is preventing WebDNA from functioning properly. > Have you ever considered this possibility? > > Have you tried to reboot the server yet to see if that > clears up the problems??? > > >> I inherited this system, and I doubt it webdna, was ever >> meant to run such a complex and large system. > You seem to think that WebDNA cannot handle large and > complex systems, which is wrong to begin with. > > But then you said the problem occurs even when there is a > light load on the server -- which suggests a WebDNA coding > error or a server misconfiguration to me. So how do you > propose to track down the problem? What is your "plan of > action"? > > >> I have to explicitly tell it from the admin panel what to >> do with it ... > What are you telling this admin panel to do? > > And what "admin panel" are you talking about? The WebDNA > admin panel that came with the WebDNA software, or a > separate programmer's admin panel? Or some other admin > panel? > > >> ... and then delte the file and let webdna make a >> new db whenever it decides to not be able to access it. > How are you deleting this file? Via an admin panel button or > link? Are you flushing the databases first BEFORE deleting > the file? How is WebDNA "making a new db" if you are > deleting the existing db? What is it using to populate this > new db? > > 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 > --=20 Med Venlig Hilsen Tommy Dahlb=E6k Bell Tlf: +45 27 63 00 88 E-mail: tbell05@student.aau.dk E-mail: tommy@enkelthed.dk
Associated Messages, from the most recent to the oldest:
No, the reason is that the entire architecture is designed around=20 windows systems - there are tons of things running on the server that=20 require windows, we are thoughouly tied into windows. Moving to LInux,=20 would require that so many services be altered into cron-jobs, and so=20 on. Not to mention the remaining software that is running on the system. Now we could get another machine to run just the webserver on, but the=20 way the system is designed/implemented, that would mean I would have to=20 change all places where webdna refers to the servers, yes I realize this=20 is a horrible way it has been done, nevertheless - that is the way it wor= ks. Hence, moving is not an option. FInally, man upstairs would never go for it, and that usually means end=20 of line anyway. -Tommy On 09-07-2011 17:43, Kenneth Grome wrote: >> Moving is simply not an option. > Why not? > > If it's Windows or IIS that's causing the problem (wow, this > would be a surprise, wouldn't it???) moving it to LInux > would be the fastest, cheapest, and most effective solution. > Why don't you try it? Is the reason because you don't know > how to admin a Linux server? > > You said the problem occurs even when the site is not busy, > so surely you could run a test on Linux to confirm or reject > the theory that it's a Windows/IIS problem and not a WebDNA > problem, right? > > >> I guess ill have to resort to the ultimate solution and >> attempt convince the man upstairs to implement a new >> system, in something other than webdna. > Are you suggesting that rebuilding the entire website in > some other software is an option -- even though it would > obviously cost thousands or tens of thousands of dollars -- > yet moving the existing site to a different server (or > properly reconfiguring the server you already have) which > would cost 2-3 order of magnitude less is NOT an option? > > Sorry, but I fail to see any logic in this at all. > > >> I realize it is not a very large DB; it only contains who >> is online, and so on, but what I am still wondering is why >> webdna is not able to write to it. > The answer is more than likely bad WebDNA code by the person > who wrote it (or modified it) or bad server configuration. Do > you have enough experience with WebDNA to be able to > diagnose a potential WebDNA problem? > > I'm willing to bet that WebDNA will work just fine on the > current server -- once you fix the server or the WebDNA code > that is causing this problem. > > >> yes it is doing this, even when there is not heavy load > After more than 16 years of programming WebDNA I have yet to > see a problem like this that I cannot fix -- especially one > where the problem is reportedly NOT due to extremely heavy > traffic on the server! > > >> our visitor >> numbers have dropped significantly, we explain it by the >> myriad of problems we've been having with webdna ... > Maybe these "problems" are caused by a badly configured IIS > server that is preventing WebDNA from functioning properly. > Have you ever considered this possibility? > > Have you tried to reboot the server yet to see if that > clears up the problems??? > > >> I inherited this system, and I doubt it webdna, was ever >> meant to run such a complex and large system. > You seem to think that WebDNA cannot handle large and > complex systems, which is wrong to begin with. > > But then you said the problem occurs even when there is a > light load on the server -- which suggests a WebDNA coding > error or a server misconfiguration to me. So how do you > propose to track down the problem? What is your "plan of > action"? > > >> I have to explicitly tell it from the admin panel what to >> do with it ... > What are you telling this admin panel to do? > > And what "admin panel" are you talking about? The WebDNA > admin panel that came with the WebDNA software, or a > separate programmer's admin panel? Or some other admin > panel? > > >> ... and then delte the file and let webdna make a >> new db whenever it decides to not be able to access it. > How are you deleting this file? Via an admin panel button or > link? Are you flushing the databases first BEFORE deleting > the file? How is WebDNA "making a new db" if you are > deleting the existing db? What is it using to populate this > new db? > > 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 > --=20 Med Venlig Hilsen Tommy Dahlb=E6k Bell Tlf: +45 27 63 00 88 E-mail: tbell05@student.aau.dk E-mail: tommy@enkelthed.dk
Tommy Bell
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:
Emailer choke (1997)
New iMac, now ... how do I make webdna serve .html files? (2005)
Setting up WebCatalog with Retail Pro data (1996)
WebCatalog f2 Installation (1997)
lookup and two records? (1997)
mySQL or MS SQL (2000)
More Applescript (1997)
Passing Variables to a [shell scriptid=123][/shell] context (2004)
Fields font size (2003)
Not really WebCat- (1997)
[WebDNA] CMS (open code) (2009)
Getting Averages for online form. (1999)
[BULK] [WebDNA] [BULK] WebDNA AJAX example wanted! (2010)
Displaying xx number of characters (1997)
[subtotal] and others (1997)
Search design (1997)
Forms Search Questions (1997)
[TaxTotal] (1998)
Purchased cart being overwritten (1997)
Weird Cookie Problem Part 2 (2007)