yippiekyyay
Programmer
Hello,
I've been getting a lot of errors on my site lately that seems to relate to CFLOCK. As the pages throw errors, I comment out the offending locks and then things run smoothly. Of course this is not a good solution because I also had to comment out a couple of custom tag calls (because they use CFLOCK in them) which I need to have running and I know work because they have for years and other sites continue to use them without problems.
The other curious thing about this situation is the consistency. Every morning for over a week now I've come in and seen that my site was throwing the error. I comment out the locks and everything goes back running slick as ever. After a couple of hours, I later take out the comments (putting the cflocks back in the code) and everything continues to work fine. Until the next morning, where all this repeats... ???
One of my colleagues has a theory that I've accidentally created a deadlock somewhere which does sound like a good explanation but I'm not sure how to go about tracking that down. I was wondering if anyone had any debugging tips for me to track down the problem or has run into something similar ...?
Thanks in advance!
I've been getting a lot of errors on my site lately that seems to relate to CFLOCK. As the pages throw errors, I comment out the offending locks and then things run smoothly. Of course this is not a good solution because I also had to comment out a couple of custom tag calls (because they use CFLOCK in them) which I need to have running and I know work because they have for years and other sites continue to use them without problems.
The other curious thing about this situation is the consistency. Every morning for over a week now I've come in and seen that my site was throwing the error. I comment out the locks and everything goes back running slick as ever. After a couple of hours, I later take out the comments (putting the cflocks back in the code) and everything continues to work fine. Until the next morning, where all this repeats... ???
One of my colleagues has a theory that I've accidentally created a deadlock somewhere which does sound like a good explanation but I'm not sure how to go about tracking that down. I was wondering if anyone had any debugging tips for me to track down the problem or has run into something similar ...?
Thanks in advance!