IN Cf admin you have a max number of concurrent requests. If all of those requests hang, then cf will start queuing requests, which is probably why your seeing 500. You need to look at the hung requests and see why they are hanging. Have you tried the built in server monitor ? If you do not have this (requires enterprise edition) then try fusion-reactor,. and also be sure you use the jdbc wrapper on your DSN's to do JDBC traces. the most common cause for hung requests that will not finsih is either database activity or IO activity which are Native java calls which cannot be killed automatically by CF's timeout.
Only CFM/cfc and related files are served by ColdFusion, your JS files are served directly by the web server, so these would not contribute to the coldfusion traffic or number of requests. If those JS files contain ajax requests to the CF server, then this will happen after the page renders in the client and the js has fully loaded. On Tue, Aug 14, 2012 at 5:49 PM, Steve LaBadie <[email protected]>wrote: > > We deployed a new website several weeks ago. > The average number of jqueries served before July-19 was ~2000 a day; > now we are serving ~45,000. > > The resources that are the most exhaustive are the following: > 1. /js/jquery.bxSlider.min.js > 2. /js/jquery.nivo.slider.home.js > 3. /js/jquery.colorbox_min.js > 4. /js/jquery.tablesorter.min.js > 5. /js/jquery-ui-1.8.20.custom.min.js > 6. /css/jqueryUI.css > > Also, the rich format of the new website is taxing the ColdFusion > engine. > When the website seems to stop, the number of connections to CF's port > 51011 increase from about 5 (average normal) to about 500. > These are TCP connections that take minutes to clear. Some stay in a FIN > state (finishing) for a few minutes before actually closing. > CPU and Memory resources are steadily low when this hang-up happens > (therefore not a Hardware or an OS problem). > > Steve LaBadie, Web Manager > East Stroudsburg University > 570-422-3999 > [email protected] > > > > -----Original Message----- > From: Cameron Childress [mailto:[email protected]] > Sent: Tuesday, August 14, 2012 12:13 PM > To: cf-talk > Subject: Re: Port 51011 > > > As Russ alluded to, ports in the 51000 range are used by the ColdFusion > Connector (that connects CF and the WebServer). So, getting alot of > requests via that Port may be totally expected, as long as it's requests > between CF and IIS. > > Are you sure this is the CAUSE of performance problems? If you're seeing > those connections and just assuming "well, that can't be good", you > might be looking at a red herring here. you're real problem may lie > elsewhere. > > In any case, when the CF Connector starts acting screwy, sometimes it's > best just to remove and recreate it. Otfen you won't know what went > wrong, just that it started working again. > > Also - don't attempt to do that unless you know what you are doing, > which hopefully you do. > > -Cameron > > On Tue, Aug 14, 2012 at 10:47 AM, Steve LaBadie > <[email protected]>wrote: > > > I have never encounter this problem before, but we are getting a lot > > of request through port 51011 which is preventing our pages from > resolving. > > We are currently using MX 7 IIS6. We have been running with version 7 > > since it came out and have never had this issue arise before. Can > > anyone give any insight as to what to do to remedy this problem? > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352151 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
