Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106895
interpreted = N
texte = Hey Tom, No worries about the previous emails, we have all had days like that. Let's just move this forward to and see if we cannot find a solution for those who are having this issue. Like I said, I saw several appearing in Google searches, Stuart, and you. I cannot say that the code you got is bad or good, but what I can say is that WebDNA is a "tag" based language, and as such you will often end up with very linear coding style. This can and often does lead to a lot of repeated code in many of the templates. If you are coming from an OO background then this is going to seem quite counterproductive to you. But it does allow for quick code, but it can wreck havoc from a maintenance standpoint. Many tags have been added over the years to help with this, functions being one of the large ones. Over the years many of us have learned to build up code libraries that we can call into our pages using includes, but this does little for old legacy script. The tag resource on WebDNA.us is perhaps one of the best tools (that I know of) but I know how you feel. When I got hired by SmithMicro and was handed WebDNA I was completely lost. But then I went on to start my own development firm and continued to use for 10 years. =3D) While I am no MSSQL expert I would suggest that you set the app pool to recycle a lot more often. You can do this either from a memory usage or # requests processed point. This problem on top of the DB Lock issue you are having, I am starting to question if your company shouldn't consider an IT Manager that knows Windows. How much access do you have to the server(s)? I am also curious if Stuart is connecting to an MSSQL database. Is this issue coming from the MSSQL database connection rather than the native flat-file system. I know I have in MSSQL hell right how with a PHP project and know that it can be temperamental with drivers and what not. Then their is the mention that it seems to be coming from a template that is sharing code. The only reason I am doubting this has anything to do with it is that Stuart mentioned his system was working fine for about 5 years and the issue is recent. Putting that aside, have you considered duplicating this file and giving some of the templates their own copy of this file to see if it helps? Since I do not know how these sites are framed out I cannot make any real code related suggestions that may aid in this, but it is quite intriguing that it is happening "all of a sudden." You said that moving to Linux was not a viable solution. Which I understand, but do you have another windows server that you could migrate the WebDNA server to in order to see if the issue persists? Also you might consider contracting someone for a day or two and giving them access to the servers to see if they can troubleshoot this for you. Sometimes a fresh set of eyes can help. Obviously get someone you can trust and consider using some sort of NDA or other agreement. Best of luck. Sincerely, Ron On Sun, Jul 10, 2011 at 11:25 PM, Tommy Bell
wrote: > Ken, > I do apologise for not answering your questions, I must have missed it wh= en > I replied to another email. > > And I shouldn't have bashed on webdna, that was an error on my part. I wa= s > simply frustrated at the lack of documentation and general knowlegde abou= t > the system from my part and the company i work at. > The previous developer has left no documentation of anything so I have to > figure out everything from the ground up again. > > This unfortunately spilled into my email. > > /Tommy > > On 10-07-2011 23:17, Kenneth Grome wrote: >> >> I have little patience with people who come here and >> complain, then refuse to cooperate when we try to help. =A0I >> had to ask him *twice* for answers to some important >> questions yet he still hasn't answered -- so does he want >> our help or not??? >> >> As Chris said, he hasn't provided a shred of evidence that >> this is a WebDNA problem. =A0This could easily be a Windows >> issue which would be identified in a couple of hours if he >> just copies the site to a Linux server and learns that he >> cannot reproduce the problem there. >> >> This is why I agree with Chris that a couple hours to >> install and test the site on a Linux server is an excellent >> way to "cut through the crap" and possibly identify the >> source of the problem very quickly. =A0If the issue goes away >> on Linux we have strong evidence that Windows is the culprit >> rather than WebDNA. >> >> And isn't the goal in a situation like this to identify the >> source of the problem in the least amount of time? =A0It would >> be for me, especially if the server's traffic were important >> to me. >> >> 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 >> > > > -- > Med Venlig Hilsen > Tommy Dahlb=E6k Bell > > Tlf: +45 27 63 00 88 > > E-mail: tbell05@student.aau.dk > E-mail: tommy@enkelthed.dk > > --------------------------------------------------------- > 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:
Hey Tom, No worries about the previous emails, we have all had days like that. Let's just move this forward to and see if we cannot find a solution for those who are having this issue. Like I said, I saw several appearing in Google searches, Stuart, and you. I cannot say that the code you got is bad or good, but what I can say is that WebDNA is a "tag" based language, and as such you will often end up with very linear coding style. This can and often does lead to a lot of repeated code in many of the templates. If you are coming from an OO background then this is going to seem quite counterproductive to you. But it does allow for quick code, but it can wreck havoc from a maintenance standpoint. Many tags have been added over the years to help with this, functions being one of the large ones. Over the years many of us have learned to build up code libraries that we can call into our pages using includes, but this does little for old legacy script. The tag resource on WebDNA.us is perhaps one of the best tools (that I know of) but I know how you feel. When I got hired by SmithMicro and was handed WebDNA I was completely lost. But then I went on to start my own development firm and continued to use for 10 years. =3D) While I am no MSSQL expert I would suggest that you set the app pool to recycle a lot more often. You can do this either from a memory usage or # requests processed point. This problem on top of the DB Lock issue you are having, I am starting to question if your company shouldn't consider an IT Manager that knows Windows. How much access do you have to the server(s)? I am also curious if Stuart is connecting to an MSSQL database. Is this issue coming from the MSSQL database connection rather than the native flat-file system. I know I have in MSSQL hell right how with a PHP project and know that it can be temperamental with drivers and what not. Then their is the mention that it seems to be coming from a template that is sharing code. The only reason I am doubting this has anything to do with it is that Stuart mentioned his system was working fine for about 5 years and the issue is recent. Putting that aside, have you considered duplicating this file and giving some of the templates their own copy of this file to see if it helps? Since I do not know how these sites are framed out I cannot make any real code related suggestions that may aid in this, but it is quite intriguing that it is happening "all of a sudden." You said that moving to Linux was not a viable solution. Which I understand, but do you have another windows server that you could migrate the WebDNA server to in order to see if the issue persists? Also you might consider contracting someone for a day or two and giving them access to the servers to see if they can troubleshoot this for you. Sometimes a fresh set of eyes can help. Obviously get someone you can trust and consider using some sort of NDA or other agreement. Best of luck. Sincerely, Ron On Sun, Jul 10, 2011 at 11:25 PM, Tommy Bell wrote: > Ken, > I do apologise for not answering your questions, I must have missed it wh= en > I replied to another email. > > And I shouldn't have bashed on webdna, that was an error on my part. I wa= s > simply frustrated at the lack of documentation and general knowlegde abou= t > the system from my part and the company i work at. > The previous developer has left no documentation of anything so I have to > figure out everything from the ground up again. > > This unfortunately spilled into my email. > > /Tommy > > On 10-07-2011 23:17, Kenneth Grome wrote: >> >> I have little patience with people who come here and >> complain, then refuse to cooperate when we try to help. =A0I >> had to ask him *twice* for answers to some important >> questions yet he still hasn't answered -- so does he want >> our help or not??? >> >> As Chris said, he hasn't provided a shred of evidence that >> this is a WebDNA problem. =A0This could easily be a Windows >> issue which would be identified in a couple of hours if he >> just copies the site to a Linux server and learns that he >> cannot reproduce the problem there. >> >> This is why I agree with Chris that a couple hours to >> install and test the site on a Linux server is an excellent >> way to "cut through the crap" and possibly identify the >> source of the problem very quickly. =A0If the issue goes away >> on Linux we have strong evidence that Windows is the culprit >> rather than WebDNA. >> >> And isn't the goal in a situation like this to identify the >> source of the problem in the least amount of time? =A0It would >> be for me, especially if the server's traffic were important >> to me. >> >> 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 >> > > > -- > Med Venlig Hilsen > Tommy Dahlb=E6k Bell > > Tlf: +45 27 63 00 88 > > E-mail: tbell05@student.aau.dk > E-mail: tommy@enkelthed.dk > > --------------------------------------------------------- > 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 >
Ronald Kirkland
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:
Tea Room trouble (1997)
WebCommerce: Folder organization ? (1997)
[WebDNA] php/mySQL version of WebDNA Speed Test? (2009)
It just Does't add up!!! (1997)
Sample Tearoom Search Error (1997)
Netscape (2002)
Database files & W2000 (2001)
Date problems-more (1997)
Duplicate Carts (2000)
Rumpus/Typhoon modules included in Typhoon ... (1997)
Customer - again (1998)
HELP WITH DATES (1997)
encrypt method=APOP broken or just not enough docs? - wasMD5 encryption (2003)
Math with Time (1997)
WebCat2b13MacPlugIn - syntax to convert date (1997)
[WriteFile] problems (1997)
Blowback and budgets. (2000)
Limitations on fields? Server is crashing (1997)
WebCat2b15MacPlugin - showing [math] (1997)
Cancel Subscription (1996)