Logging.jsp is a useful page. It allows changing jboss (including Identity Manager’s) logging levels on the fly without a need for recycle. This is especially handy in a Production environment that can not be restarted on-demand.
However, if requests are no longer accepted by jboss, then you will be unable to make changes to logging.jsp and will result with this error below:
JBWEB002004: More than the maximum number of request parameters (GET plus POST) for a single request (512) were detected.
This doc explains the nature of this error, how to avoid and handle it. See included file for error message.
Requests to logging.jsp are being served by jboss system threads. If these threads are all maxed out, then you may run into the earlier error. This is an issue of jboss administration, not of Identity Manager.
There are a number of ways to handle this:
1. Active monitoring of your jboss, using the jboss administration console. Alternatively or alongside that, you may occasionally restart your jboss server. This will reset its system threads, ensure they are back to normal levels and start over. It can be seen as a preventative or cautionary measure not to run into such situations.
The frequency of this monitoring or recycle really depends on the level of use of your jboss. If heavily used then more threads are in-the-works and chances of this situation are higher.
2. Extending the allowed number of requests. You can increase the jboss system parameter to give more room to serve more requests. See the instructions section below to learn how this is done.
Applies to Identity Manager 12.0, 12.5 and 12.6.
Relates to JBoss 6.x.
Step 1: Open standalone.xml file available in "<JBOSS_HOME>\standalone\configuration" folder.
Step 2: Paste below code after </extensions> tag and change value as per your requirement.
<property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/>
NOTE: You can increase the value above 5000. Recommendation is anywhere between 5000-10000.
See more on jboss system properties at: