-
1. Re: maxParameterCount on standalone configuration
jfclere Apr 18, 2012 4:10 AM (in response to hlfsousa)1 of 1 people found this helpfulyou have to use a system property org.apache.tomcat.util.http.Parameters.MAX_COUNT.
-
2. Re: maxParameterCount on standalone configuration
sergiu_pienar Jun 8, 2012 9:10 AM (in response to jfclere)Jean-Frederic,
Could you please be a bit more specific ?
Thank you.
-
3. Re: maxParameterCount on standalone configuration
jfclere Jun 8, 2012 10:28 AM (in response to sergiu_pienar)Something like:
</extensions>
<system-properties>
<property name="org.apache.tomcat.util.bla.bla" value="nnn"/>
</system-properties>
<management>
In standalone.xml
-
4. Re: maxParameterCount on standalone configuration
sergiu_pienar Jun 11, 2012 3:31 AM (in response to jfclere)Thanks!
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
-
5. Re: maxParameterCount on standalone configuration
vaibhavnaik Jul 27, 2012 9:16 AM (in response to jfclere)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.)Thanks.
-
6. Re: maxParameterCount on standalone configuration
jfclere Jul 30, 2012 3:21 AM (in response to vaibhavnaik)Using many parameters brings performances issues and risk for hash map collissions.
Usually many parameters are due to poor design of the webapps :-(
-
7. Re: maxParameterCount on standalone configuration
vaibhavnaik Jul 30, 2012 3:28 AM (in response to jfclere)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? -
9. Re: maxParameterCount on standalone configuration
technokrat Aug 15, 2012 5:51 AM (in response to hlfsousa)I spent 4 hour to find how looks bla-bla.
<system-properties>
<property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/>
</system-properties>
-
10. Re: maxParameterCount on standalone configuration
yuvraj.patel Nov 18, 2014 7:09 AM (in response to hlfsousa)Hi,
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.
Thanks
Yuvraj
-
11. Re: maxParameterCount on standalone configuration
jfclere Nov 18, 2014 10:14 AM (in response to yuvraj.patel)actually EAP5 and EAP6 have the fix.... Probably AS6 never gets it.
-
12. Re: maxParameterCount on standalone configuration
jishnunp May 24, 2017 6:51 AM (in response to hlfsousa)set "JAVA_OPTS=%JAVA_OPTS% -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1000"
this will resolve the issue
-
13. Re: maxParameterCount on standalone configuration
mingweiwu Sep 14, 2018 11:44 AM (in response to hlfsousa)For Jboss 7, EAP 6.0 change the Parameters.MAX_COUNT value = "-1" in standalone.xml will works