000032577 - When scheduling the collectors in RSA Identity Governance and Lifecycle 7.0 and higher the following error is seen:  The number of parameters exceeded the maximum of 1000

Document created by RSA Customer Support Employee on Jun 20, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000032577
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle 
RSA Version/Condition: 7.0 and higher
Application Server : WildFly
IssueWhen trying to schedule multiple collectors via Collectors > Scheduling, the page does not respond properly and the following error is thrown in the aveksaServer.log
06/14/2017 21:21:40.958 ERROR (default task-355) [com.aveksa.gui.core.filters.LoginFilter] 
java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000
at io.undertow.server.handlers.form.FormData.add(FormData.java:77)
at io.undertow.server.handlers.form.FormData.add(FormData.java:67)
at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.doParse(FormEncodedDataDefinition.java:172)
at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.parseBlocking(FormEncodedDataDefinition.java:251)
at io.undertow.servlet.spec.HttpServletRequestImpl.parseFormData(HttpServletRequestImpl.java:752)
at io.undertow.servlet.spec.HttpServletRequestImpl.getParameter(HttpServletRequestImpl.java:626)
at javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194)
at com.aveksa.gui.util.security.XSSRequestWrapper.getParameter(XSSRequestWrapper.java:65)
CauseThe issue occurs if you have more than 100 collectors of the same collector type.  Each collector holds approximately ten parameters and having more than 100 collectors for any collector type may exceed the WildFly application server default maximum parameters threshold of 1000.
ResolutionThis issue has been resolved in the following releases:
  • 7.0.0 P05 and higher
  • 7.0.1 P01 and higher
  • 7.0.2 and higher
Please update accordingly.
WorkaroundAs a workaround, you can manually edit the /home/oracle/wildfly/standalone/configurationaveksa-standalone-full.xml and increase the limit. 
In the example below, the limit is increased from the default of 1000 to 3000 by adding max-parameters="3000" under urn:jboss:domain:undertow:1:2. The value of 3000 is just an example. To calculate an appropriate value for your site, multiply the number of your collectors by ten. For example, if you have 400 collectors for a given collector type, set max-parameters="4000".
                "default" socket-binding="http" max-post-size="2147483647" max-parameters="3000"/>
                "agent-ssl" socket-binding="agent-ssl" max-parameters="3000" security-realm="AveksaAgentRealm" verify-client="REQUIRED" enabled-protocols="TLSv1.2" max-post-size="2147483647"/>
                "https" socket-binding="https" max-parameters="3000" security-realm="AveksaRealm" enabled-protocols="TLSv1,TLSv1.1,TLSv1.2" max-post-size="2147483647"/>
                "default-host" alias="localhost">