Why is there a max of 25 requests in Coldfusion 9?

[Splimpt]

Hey

Does anyone know why Coldfusion 9 seems to have an arbitrary limit of 25 requests whether they are running or queued or a combination of the two?

This behavior was not in CF8...

Here are 3 screenshots that show what I mean.

[BKBK]

Why is there a max of 25 requests in Coldfusion 9?

The very next setting on that Coldfusion Administrator page tells you why. The setting, "Maximum number of running JRun threads", is the upper bound for the total number of the 4 types of request, template, Flash, Web Service, CFC function.That is,

Maximum number of simultaneous Template requests
+
Maximum number of simultaneous Flash Remoting requests
+
Maximum number of simultaneous Web Service requests
+
Maximum number of simultaneous CFC function requests

<=

Maximum number of running JRun threads

The total for your current settings is 25+5+5+10, or 45. If you wish to go beyond that, you have to increase the setting for maximum number of JRun threads to 46 or more.

[inteppa]

While that might make sense, if you look at my CFSTAT screenshots, the max is 25 not 45.

That's the question being asked.

[ilssac]

I THINK what BKBK is telling you is that you have a TOTAL MAXIMUM of ALL types of threads of 45.

Then if you subtract 5 threads you allowed for Flash remoting requests

AND

5 Threads for Web Services requests

AND

10 Threads for CFC requests

That leaves only 25 threads for template threads.

So IF you only increase the allowed number of template threads, but you don't increase the maximum for all types of threads OR reduce one of the other types of threads the same amount, then the former does not do much

[BKBK]

While that might make sense, if you look at my CFSTAT screenshots, the max is 25 not 45.

That's the question being asked.

What I gave is a possible answer. Please read it.

The setting for maximum number of JRun threads is the upper limit for the sum total of all 4 types of request. Your setting is probably 45.

That would explain why you're unable to go past 25. Tthe other 3 request types add up to 20, and 25+20=45. Do you see where the 45 comes from?

To verify, increase the setting for maximum number of JRun threads to 60, say. The number of requests should now exceed 25. Does it?

[inteppa]

Thanks for clarifying that.

I have already tried tweaking the maximum jrun threads.  It is currently set at 100 but still shows no change beyond the 25.

I hope that makes more sense now as to my problem!

[BKBK]

After you make the setting for the maximum number of JRun threads, press the button to submit the changes. Do you get something similar to the resultin my image?

In my particular case, the value should be more than the sum 46. What is the sum in your case?

[inteppa]

Hello, yes, after hitting submit that value does change.  It did get cut off in my previous screenshot, but it is 46.

I've included everything below:

[BKBK]

So far, there are apparently no issues. As the heading says, now you only have to restart Coldfusion for the JRun settings to take effect.

[inteppa]

Issues still exist.  Already restarted CF for settings to take effect many times.  Again, results of cfstat show 25 still the max.

Is anyone aware if or how IIS6 could be limiting requests?  (not connections, I can see there are over 180 ppl on the site)

[BKBK]

Is anyone aware if or how IIS6 could be limiting requests?

Funny you should say that. 25 requests in IIS rings a bell. It is the default value for the limit of the number of Threads Per Processor.

It is recommended to keep this setting to 100 or less. To change the setting, follow the steps in Microsoft's documentation, Tune the value of the ASP Threads Per Processor Limit property.

[inteppa]

Thank you for that tip.

I was excited when you pointed out the correlation of the 25 ASPProcessorThreadMax setting being the default.

Sadly, I altered that setting to 40 with no change in behavior.  I wonder if that only relates to ASP requests.  That seemed pretty close, though.

[inteppa]

This issue was finally resolved by Adobe.

I am posting the resolution here in case anyone might come across the same situation.  I'm surprised no one out there has noticed this (assuming they are running a high traffic site with IIS6 and CF9)...

Anyway, the solution by Kunal Sunai at Adobe:

You can increase number of IIS6 worker threads, by default it is 25.

1.    Go to <cf9_install_location>\runtime\lib\wsconfig\1
2.    Open jrun_iis6_wildcard.ini
3.    Uncomment maxworkerthreads=25
4.    Change the value of maxworkerthreads=50 and restart iis.

This should resolve your problem.

Thanks for your help in this thread, BKBK.

[BKBK]

This issue was finally resolved by Adobe.

I am posting the resolution here in case anyone might come across the
same situation.  I'm surprised no one out there has noticed this
(assuming they are running a high traffic site with IIS6 and CF9)...

I share your surprise. In my opinion, this is one of the most astonishing questions so far in the forum, and certainly one of the most important.