I wish it was, but we have only one app on the server, and it does not use session variables and the application var usage has been thoroughly reviewed and the locks appear correct.
The application vars used by the app are refreshed essentially once a day or when they do not exist (isdefined), these locks would not have been in effect at the time of these crashed. The application vars would have been being read but not written. This is the case throughout the site with no exceptions. There are several 3rd party calls, and I had thought initially that this was the problem. But I am not alone with this problem as it seems Tyler is with his "Success" stories. Tyler, do you think every one in this thread has some application issues and that we should all stop blaming CFMX and use your limited success as proof that CFMX works under load? http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=143&threadi d=468954 Brook At 02:58 PM 27/11/02 -0800, you wrote: >Off the top of my head and perhaps worth just that... > >Could you have a deadlock condition going? ... Locking A&B on one request >and another near simultaneous request locking B&A such that each are >waiting on the other to finish and release the lock so that they can exert >their second lock and continue? > >Just an off the wall thought from previous experiences with "other" systems. > > > > > >At 02:45 PM 11/27/02, you wrote: > >Well, our CFMX server just crashed for the 4th time today. I've had the > >perfmon open all day and have been watching the traffic. We had an average > >of 12 connections when the running requests started to grow and grow. As I > >mentioned in my previous post, there were 3 running requests that had not > >finished for hours. As far as the number of CFMX request, as I was watching > >it, it never went above 6. This really means there was a max of 3 running > >requests (on top of the 3 that were already dead), it would go up to 6 and > >then back down to 3. Those 3 threads weren't going anywhere. > > > >Then I noticed that the running requests was growing incrementally, so I > >tried to make an HTTP request to the server....and it did not respond. I > >checked the running requests, and there was one more. The server was DEAD, > >HUNG, FINISHED - KAPUT. > > > >The Perfmon counter restarted jrun when the running requests reached 10, > >and the server came back to life. Thank you Lee Fuller for this > temporary fix. > > > >What is Macromedia doing about this? CFMX is not ready for production. If > >your sales of CFMX are not what you expected, there's a fairly obvious > >reason why. I certainly, based on my experience, would not recommend (and I > >think anyone running CFMX would agree) anyone to switch to CFMX anytime > >soon. Unless you have plenty of spare time to baby sit your server. > > > >Brook > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
