tracker issue : CF-4205374

select a category, or use search below
(searches all categories and all time range)
Title:

Unable to update Maximum size of post data and other settings

| View in Tracker

Status/Resolution/Reason: Open//

Reporter/Name(from Bugbase): Rocky R. / ()

Created: 10/08/2019

Components: Administrator, Administrator Console

Versions: 2018

Failure Type: Usability Issue

Found In Build/Fixed In Build: 2018.0.04.314546 /

Priority/Frequency: Normal / Unknown

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:
In CF 2018 Standard Edition, Update 4, Production+Secure Profile, I'm unable to change the value for "Maximum size of post data" in the console. I had to change the value manually in neo-runtime.xml file. When I change the value in the console and hit submit, the console returned unrelated warnings and did not change the post data value. When I tried to also address the unrelated warnings, those values also were not changed. 

Steps to Reproduce:
In the Administrator console, change the default value for Maximum size of post data and submit changes.

Actual Result:
Value for Maximum size of post data is unchanged, both in the console and in the neo-runtime.xml file. Instead, console displays the following warnings:
- Core pool size is too large for Standard edition (I hadn't changed this)
- Maximum pool size is too large for Standard edition (I hadn't changed this)
- Missing template handler does not exist (it does exist, and in fact the same file is specified for the Site-wide error handler, which is working). Also the handler value had been updated to the default template.

I changed the pool size values to 10 (the recommended values), left the default template as the missing template handler and submitted again but still got errors and the Maximum post size value still was unchanged.

Expected Result:
The Maximum post size value should be updated.

Any Workarounds:
Manually change the value for the Maximum size of post data in the neo-runtime.xml file, then restart CF.

Attachments:

Comments: