KB-1535 Header count exceeded allowed maximum [128]

Jordan Horwat — Mon, 23 Jul 2018 10:24:42 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 10:24:42 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6.4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, infrastructure, jboss

KB-1535 Header count exceeded allowed maximum [128]

Parmida Borhani — Tue, 03 Apr 2018 08:04:12 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 4/3/2018 8:04:12 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6.4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

KB-1535 Header count exceeded allowed maximum [128]

Parmida Borhani — Tue, 03 Apr 2018 04:04:12 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 4/3/2018 4:04:12 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6.4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Parmida Borhani — Tue, 03 Apr 2018 04:03:22 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 4/3/2018 4:03:22 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6.4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Thu, 29 Mar 2018 04:26:06 GMT

Revision 7 posted to Appian Knowledge Base by Sean Kim on 3/29/2018 4:26:06 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6..4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Thu, 29 Mar 2018 04:25:00 GMT

Revision 6 posted to Appian Knowledge Base by Sean Kim on 3/29/2018 4:25:00 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6..4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Thu, 29 Mar 2018 04:09:41 GMT

Revision 5 posted to Appian Knowledge Base by Sean Kim on 3/29/2018 4:09:41 AM

Symptoms

When users try to access alerts or process details for a process instance in /designer, they may run into an error in the UI like the following:

Users will also see the following error in the JBoss server.log:

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop the application server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml.
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>.
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the application server.

Affected Versions

This article applies to all versions of Appian using JBoss EAP 6..4.x as an application server.

Last Reviewed: April 2018

Tags: application server, designer, jboss

Header count exceeded allowed maximum [128]

Sean Kim — Wed, 28 Mar 2018 15:13:38 GMT

Revision 1 posted to Appian Knowledge Base by Sean Kim on 3/28/2018 3:13:38 PM

Symptoms

Symptoms of the issue include:

Unable to access alerts in /designer.
Unable to access process details for a process instance.

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop Application Server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the Application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Wed, 28 Mar 2018 11:18:23 GMT

Revision 4 posted to Appian Knowledge Base by Sean Kim on 3/28/2018 11:18:23 AM

Symptoms

Symptoms of the issue include:

Unable to access alerts in /designer.
Unable to access process details for a process instance.

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop Application Server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the Application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Wed, 28 Mar 2018 11:15:28 GMT

Revision 3 posted to Appian Knowledge Base by Sean Kim on 3/28/2018 11:15:28 AM

Symptoms

Symptoms of the issue include:

Unable to access alerts in /designer.
Unable to access process details for a process instance.

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop Application Server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the Application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: application server, designer, jboss

DRAFT KB-XXXX Header count exceeded allowed maximum [128]

Sean Kim — Wed, 28 Mar 2018 11:15:15 GMT

Revision 2 posted to Appian Knowledge Base by Sean Kim on 3/28/2018 11:15:15 AM

Symptoms

Symptoms of the issue include:

Unable to access alerts in /designer.
Unable to access process details for a process instance.

java.lang.IllegalStateException: JBWEB002005: Header count exceeded allowed maximum [128]

Cause

The JBoss container limits the Mime Header count to 128 by default. This header count is related to how resources in the /designer interface are accessed.

Workaround

To resolve the issue, perform the following:

Stop Application Server.
Navigate to <JBOSS_HOME>/standalone/configuration/standalone.xml
Inside the standalone.xml file, locate the following: <system-properties><property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="5000"/></system-properties>
Add the following property to the <system-properties> section: <property name="org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT" value="512"/>. This increases the Mime Header count from the default 128 to 512.
Save the file and start the Application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2018

Tags: application server, designer, jboss