Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106893
interpreted = N
texte = Ken, yes it would appear I do have my answer, quicker than I was able to=20 answer all the emails that came in on my previously submitted emails. I will take the time to just address a few of them though. Ronald, Yes, sorry I've become very frustrated with this whole system. While I=20 don't doubt it can be used to build large and complex systems, if you=20 know what you are doing. Then I shall happily admit, I havent got a=20 clue, when it comes to webDNA; further I inherited this system, I did=20 not design it nor implemented it, I have been killing bugs ever since I=20 got involved in it 5 years ago. During those 5 years, I've learned=20 enough of webDNA to usually solve the problems and develop some minor=20 scripts, I am by no means an expert and have never claimed to be. Having=20 said that, I do regret simply blurting out that I should simply move the=20 entire thing to another language, that wont solve the problem. I believe=20 the flaw in the system is the design of it, not so much the language it=20 is implemented in. This is an issue that goes back until when the system=20 was first purchased by a company that delivered an unfinished product,=20 which the employees then began fixing and expanding, resulting in the=20 mess it is now. Again, not the fault of the language. Moving it to=20 another language is not an option anyway. I don't know what others considers a large system, but last I checked,=20 about a year and a half ago. it was 250.000 lines, this is both=20 presentation(html) and webdna logic. I find that to be a large site as=20 other systems I've worked on that does 10 times more, does not even=20 contain 50.000 lines of logic code, and the presentation logic is not=20 tied into it. Again this could be the fault of the original implementors=20 and the modifications done over the years and not the fault of webdna. Ken, in one of your previous mails you asked about the admin panel. The admin system I am refering to is the admin/index.tpl that I believe=20 is included in the webcatalog release. However as this is an inherited=20 system, I am not sure. There are options in this for showing the=20 triggers, sandbox versions, show databases, commit and flush databases=20 and a few others. And I do apologise for not including enough information in my post,=20 about the problem. As Stuart mentions, "It does seem to be coming regularly from one template that shares a=20 heap of code with other templates." - Stuart This is also the case with my system, the code is shared between other=20 templates and the combined code is big, atleast from what I have seen. IN general, if someone has something I could read to get more up to=20 speed on general workings of webdna, I would be very much interested, so=20 far I've gotten by, by patching things together from the manual and the=20 code that is already present in the system, simply continueing the same=20 code design (this leeds to problems if the code design is poor - which I=20 admittedly already know it is, I simply do not have the competences to=20 change it using webdna). I mentioned earlier the system is 250.000 lines of presentation and=20 webdna logic, I think this is a large system? It is backed by a few=20 remaining flat file db's, and a MSSQL server, which also poses problems,=20 as webdna does not appear to close the db connections, and sooner or=20 later the sql server has to be restartet or some piece of sql code=20 executed to drop the connections. This is a whole other issue, but I=20 spoke with Chris earlier that the sql release only works with mysql I=20 think he replied. All in all, thanks for the assistance I am sorry I was not able to=20 provide more information more speedily for a resolution of this problem.=20 Seaching the internet, I have come across others that have had the same=20 problem, but I feel there is a lack of forum where these sorts of things=20 can be addressed. Somewhere along the line, this issue might appear=20 again somewhere else and someone will either have to figure it out=20 themselves or post another question to the mailling list. But again,=20 that would require active users which are interested in sharing=20 solutions and so on. /Tommy On 11-07-2011 01:59, Kenneth Grome wrote: >> I reported the same problem last >> week on a system that has been running for 5+ years and >> have NEVER seen the problem in 12+ years of WebDNA >> experience. > Maybe it is caused by a somewhat recent upgrade on Windows > servers? > >> After reading the many rants in this thread I do suspect >> that it MAY be a Windows problem brought about from a >> Windows update. >> In this case, i believe Windows (an update, a specific >> module or extension) is to blame. > It looks like a few of us are coming to a conclusion that > makes sense: WebDNA is fine, Windows is screwing things up. > > Tom, I think you have your answer. Now all someone has to > do is find a way to solve the problem ... > > 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=C3=A6k 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:
Ken, yes it would appear I do have my answer, quicker than I was able to=20 answer all the emails that came in on my previously submitted emails. I will take the time to just address a few of them though. Ronald, Yes, sorry I've become very frustrated with this whole system. While I=20 don't doubt it can be used to build large and complex systems, if you=20 know what you are doing. Then I shall happily admit, I havent got a=20 clue, when it comes to webDNA; further I inherited this system, I did=20 not design it nor implemented it, I have been killing bugs ever since I=20 got involved in it 5 years ago. During those 5 years, I've learned=20 enough of webDNA to usually solve the problems and develop some minor=20 scripts, I am by no means an expert and have never claimed to be. Having=20 said that, I do regret simply blurting out that I should simply move the=20 entire thing to another language, that wont solve the problem. I believe=20 the flaw in the system is the design of it, not so much the language it=20 is implemented in. This is an issue that goes back until when the system=20 was first purchased by a company that delivered an unfinished product,=20 which the employees then began fixing and expanding, resulting in the=20 mess it is now. Again, not the fault of the language. Moving it to=20 another language is not an option anyway. I don't know what others considers a large system, but last I checked,=20 about a year and a half ago. it was 250.000 lines, this is both=20 presentation(html) and webdna logic. I find that to be a large site as=20 other systems I've worked on that does 10 times more, does not even=20 contain 50.000 lines of logic code, and the presentation logic is not=20 tied into it. Again this could be the fault of the original implementors=20 and the modifications done over the years and not the fault of webdna. Ken, in one of your previous mails you asked about the admin panel. The admin system I am refering to is the admin/index.tpl that I believe=20 is included in the webcatalog release. However as this is an inherited=20 system, I am not sure. There are options in this for showing the=20 triggers, sandbox versions, show databases, commit and flush databases=20 and a few others. And I do apologise for not including enough information in my post,=20 about the problem. As Stuart mentions, "It does seem to be coming regularly from one template that shares a=20 heap of code with other templates." - Stuart This is also the case with my system, the code is shared between other=20 templates and the combined code is big, atleast from what I have seen. IN general, if someone has something I could read to get more up to=20 speed on general workings of webdna, I would be very much interested, so=20 far I've gotten by, by patching things together from the manual and the=20 code that is already present in the system, simply continueing the same=20 code design (this leeds to problems if the code design is poor - which I=20 admittedly already know it is, I simply do not have the competences to=20 change it using webdna). I mentioned earlier the system is 250.000 lines of presentation and=20 webdna logic, I think this is a large system? It is backed by a few=20 remaining flat file db's, and a MSSQL server, which also poses problems,=20 as webdna does not appear to close the db connections, and sooner or=20 later the sql server has to be restartet or some piece of sql code=20 executed to drop the connections. This is a whole other issue, but I=20 spoke with Chris earlier that the sql release only works with mysql I=20 think he replied. All in all, thanks for the assistance I am sorry I was not able to=20 provide more information more speedily for a resolution of this problem.=20 Seaching the internet, I have come across others that have had the same=20 problem, but I feel there is a lack of forum where these sorts of things=20 can be addressed. Somewhere along the line, this issue might appear=20 again somewhere else and someone will either have to figure it out=20 themselves or post another question to the mailling list. But again,=20 that would require active users which are interested in sharing=20 solutions and so on. /Tommy On 11-07-2011 01:59, Kenneth Grome wrote: >> I reported the same problem last >> week on a system that has been running for 5+ years and >> have NEVER seen the problem in 12+ years of WebDNA >> experience. > Maybe it is caused by a somewhat recent upgrade on Windows > servers? > >> After reading the many rants in this thread I do suspect >> that it MAY be a Windows problem brought about from a >> Windows update. >> In this case, i believe Windows (an update, a specific >> module or extension) is to blame. > It looks like a few of us are coming to a conclusion that > makes sense: WebDNA is fine, Windows is screwing things up. > > Tom, I think you have your answer. Now all someone has to > do is find a way to solve the problem ... > > 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=C3=A6k 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:
Menu Madness (2001)
[WebDNA] switch / case value=% BUG? (2020)
more multiple items to shopping cart (2000)
bug in listwords? (1998)
automating txt downloads for conversion to webcat db (2006)
[isfolder] and [filename] (1997)
Online reference (1997)
Webcat 2.0.1 date math bug -> Crash! (1997)
WebStar 3 crackable !!!! (1998)
[OT] MacOs IE5 topmargin and leftmargin bug (2000)
I want a 404 (2005)
wc 2 pro users - sites, quotes wanted (1997)
RE: [WebDNA] Installation problems for IIS 6 (2010)
blank page from template (1997)
Week # problem (1998)
Summing fields (1997)
searching problem (1998)
WebCat2b13 Command Reference Doc error (1997)
& not allowed in db by definition? (1999)
emailer on Windows Beta 18 (1997)