Skip to main content
wog_ch
wog_ch
Participating Frequently
January 28, 2020
Question

Cannot change 'Request Limits' / Error: Cannot find attribute [maxThreads]

  • January 28, 2020
  • 1 reply
  • 1234 views

Coldfusion Administrator CF 2018

Problem Description:
Up to Hotfix 4 OK but with Hotfix 5 or higher it is not possible to change 'Maximum number of simultaneous Template requests' in CF-Administrator/Request Tuning/Request Limits:
By clicking to 'Submit changes' the info will show: 'Server has been updated successfully' but the page refreshes with the old value. Same time there is an error in the server.log:

"Error","http-nio-8500-exec-1","01/27/20","18:14:27",,"Cannot find attribute [maxThreads] on resource [org.apache.tomcat.util.net.SocketProperties@50f4bdef]"

 

System:

With Linux or Windows and Developer Edition, there is no Error
Windows with Standard Edition --> Error (Same error on two different Systems)


CF10 was installed, CF 2018 Installed with Migration Wizard

 

-----

Server Product ColdFusion 2018
Version 2018.0.05.315699
Tomcat Version 9.0.21.0
Edition Standard
Operating System Windows Server 2012 R2
OS Version 6.3
Adobe Driver Version 5.1.4 (Build 0001)
JVM Details
Java Version 11.0.1
Java Vendor Oracle Corporation
Java Vendor URL http://java.oracle.com/
Java Home C:\ColdFusion2018\jre

This topic has been closed for replies.

1 reply

wog_ch
wog_chAuthor
Participating Frequently
January 29, 2020

I've changed our license entry to Developer in cfusion/lib/license.properties (sn=Developer). After CF restart the change of the value of 'Maximum number of simultaneous Template requests' is possible and there is no [maxThreads] error.

 

Does anybody else have this issue?

 

wog_ch
wog_chAuthor
Participating Frequently
February 17, 2020

After changing license back to Standard Edition the error occures again. It must be a bug! Has anybody a workaround for this?!

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
February 17, 2020

Yes, someone has a fix. Have you not seem the response from Adobe, in the bug report you filed? They said (back on Jan 29) that it is fixed in update 7, which came out in December. You report here (and there) that you had this issue with update "5 or higher", but it's not clear if you have tried update 7. Let us know if that works

/Charlie (troubleshooter, carehart. org)
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices