Showing results for 
Show  only  | Search instead for 
Did you mean: 

UT000047: The number of parameters exceeded the maximum of 1000

UT000047: The number of parameters exceeded the maximum of 1000


Getting "Internal server error" is seen in the user interface. We frequently see this error when mapping an entitlement to the device if the account has a large number of entitlements.


Find the following error in Logfile:

12:03:33,520 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /flexnet/operations/fne/devices/ReveneraDevice/STRING/123456789/CLIENT/addOns: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000


This is the Wildfly (JBoss) configuration problem which has a restriction of 1000 parameters by default as part of request input (in the standalone-full.xml the default value for the max-parameters="1000"). The number of parameters was limited in all web servers to plug the hashmap collision denial of service attack. We can change the number to the required limit in the standalone-full.xml file.

We have to update the following line from:

<http-listener name="default" socket-binding="http"/>


<http-listener name="default" socket-binding="http" max-parameters="5000"/>

or even we can add Maximum value if the 5000 is not working:

<http-listener name="default" socket-binding="http" max-parameters="99999999"/>

​​​​​​​The whole block looks something like below:

<subsystem xmlns="urn:jboss:domain:undertow:1.0">
<buffer-cache buffer-size="1024" buffers-per-region="1024" max-regions="10" name="default"/>
<server name="default-server">
<http-listener name="default" socket-binding="http" max-parameters="5000"/>
<https-listener name="https" security-realm="UndertowRealm" socket-binding="https"/>
<host alias="localhost" name="default-host">
<location handler="welcome-content" name="/"/>
<filter-ref name="server-header"/>

You need to restart the FlexNet Operations server after the update.

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Feb 10, 2023 04:47 PM
Updated by: