Resource Graph Resources - limited to 55 Resources or less
Description
Environment
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Benjamin Reed April 24, 2014 at 12:29 PM
In 1.12.7, Jetty has been changed to use a jetty.xml file which can be configured to handle issues like this.
Andy Ellsworth October 21, 2011 at 4:37 PM
Steps I took to reproduce the bug that still remains:
Start with default requestHeaderSize of 4000 and HTTP only
Hit OpenNMS with a giant request ("select all" resource graphs on a LAN switch with a couple hundred ports does nicely)
Get blank page (as expected, with the default header size)
Configure the requestHeaderSize to e.g. 400000 instead of 4000 bytes
Hit OpenNMS with a giant request ("select all" resource graphs on a LAN switch with a couple hundred ports does nicely)
Works fine (as expected, with the tunable parameter mentioned in this bug)
Configure Jetty to use HTTPS instead of HTTP, and keep the large requestHeaderSize
Hit OpenNMS with a giant request ("select all" resource graphs on a LAN switch with a couple hundred ports does nicely)
(BUG) Get blank page - requestHeaderSize has been increased to 400000, and works fine with HTTP, but not HTTPS
Incidentally, the URL that was generated for my tests was approximately 14 kB.
Andy Ellsworth October 21, 2011 at 4:26 PM
The requestHeaderSize fix that is in place works for HTTP, but not for HTTPS. Confirmed on 1.9.93 snapshot.
Donald Desloge September 7, 2011 at 10:33 AM
The property is org.opennms.netmgt.jetty.requestHeaderSize, the default value is 4000, you can set it to anything larger to increase the URL length that Jetty will support.
Charles Hopkins September 7, 2011 at 7:29 AM
Can you tell us what that line needs to read?
There seems to be a limit to the number of Resource Graph Resources one can choose before the server won't spit out a response. It seems like if I choose 55 Resources that I get a served page. If I choose 56 or more I get a blank page. Someone said that it was set by a POST limit but couldn't tell me where that was set. Where would I change the POST setting?
Some of our Cisco devices run 80+ Resources listed and I know the capacity is higher.
I have tried to put variations of the following line in multiple locations each with no results
"org.mortbay.jetty.Request.maxFormContentSize=400000"
"org.mortbay.jetty.Request.maxFormContentSize=-1"
"org.mortbay.jetty.Request.maxFormContentSize=600000"
Default value is 200000 (according to "opennms.properties" among other places.
The relevant section is:
This sets the maximum size for a form submission in jetty.
The default value is 200000 bytes. Setting it to -1 disables
the form limit
#org.mortbay.jetty.Request.maxFormContentSize=200000
org.mortbay.jetty.Request.maxFormContentSize=-1
I can supposedly put a line in an "opennms.conf" file that states (or similar):
ADDITIONAL_MANAGER_OPTIONS=-Dorg.mortbay.jetty.Request.maxFormContentSize=400000
but no joy.
Thanks in advance.
Chaz