1 of 1 people found this helpful
you have to use a system property org.apache.tomcat.util.http.Parameters.MAX_COUNT.
Could you please be a bit more specific ?
<property name="org.apache.tomcat.util.bla.bla" value="nnn"/>
The same can be achieved via the Management Console @ localhost:9990 -> Profile -> General Configuration -> System Properties and add the specific key and value.
Message was edited by: Sergiu Pienar
I'm using "JBoss-EAP-6.0.0"(Evaluvation version) & facing same issue when I deployed my application in "standalone". It worked fine after modifying standalone.xml as you suggested.
My questions are:
The request params length can be huge in enterprise application. Why this restriction in request params then?
Is this same setting required for application which are deployed in "domain" too?
Is there any other workaround that I can change in my application only? (I don't want to ask customers to modify their JBoss settings. It is painful.)
Using many parameters brings performances issues and risk for hash map collissions.
Usually many parameters are due to poor design of the webapps :-(
Do I need to modify param limits for application deployed in "domain" too? Whats the default param limit for "domain"?
I think, I must have to document this workaround for cutomers. right?
I spent 4 hour to find how looks bla-bla.
<property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/>
Could anybody please let me know if there was something similar in Jboss eap 5 or have anybody seen this issue in jboss 5. Actually we have upgraded to jboss6 and getting this issue and I wanted to know as why this worked in Jboss 5 and its not working on jboss 6.
actually EAP5 and EAP6 have the fix.... Probably AS6 never gets it.
set "JAVA_OPTS=%JAVA_OPTS% -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1000"
this will resolve the issue
For Jboss 7, EAP 6.0 change the Parameters.MAX_COUNT value = "-1" in standalone.xml will works