KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Kaushal Patel — Fri, 07 Nov 2025 16:13:57 GMT

Current Revision posted to Appian Knowledge Base by Kaushal Patel on 11/7/2025 4:13:57 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

This usually occurs because the web server has received a request that is larger than the configured limit. The web server is currently configured to limit the file size and will throw an error when it receives a request that is too large.

Depending on the exact action being performed by the user, and the subsequent request being made to the web server, the error could be due to the size of the request’s header, message body or the total size of the request as a whole.

Action

To prevent this error from reoccurring, and to allow the requests to be fulfilled by the web server, raise the maximum allowed size for the area of the message (header, body, etc) that is causing the error.

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat (Appian 21.2 and later)

Add the following properties inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.ajp.maxPacketSize=24576
```
```
conf.appserver.maxHeaderSize=65535
```
Note that the default value for the maxPacketSize is set to 8192 and for the maxHeaderSize, the max is 66536.
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 21.1)

Add the following property inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.maxHeaderSize=65535
```
Note The max value for maxHeaderSize is 66536.
Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 20.4 and earlier)

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

In the Apache httpd.conf file (located in <APACHE_HOME>\conf), update or add the following properties to align with your Tomcat AJP configuration values:
- Set the maximum HTTP header field size to match the Tomcat maxHttpHeaderSize value:
```
LimitRequestFieldSize 65535
```
- Set the AJP worker packet size to match the AJP maxPacketSize configured in Tomcat’s server.xml or Appian’s custom.properties:
```
JKWorkerProperty worker.<node>.max_packet_size=X
```
  where:
  - <node> is the Tomcat/AJP worker node name defined in your Apache configuration.
  - X is the same value as your AJP maxPacketSize (for example, 24576).
Save your changes.
Restart the Apache web server for the new configuration to take effect.

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: January 2025

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

pauline.delacruz — Wed, 22 Jan 2025 22:45:59 GMT

Revision 23 posted to Appian Knowledge Base by pauline.delacruz on 1/22/2025 10:45:59 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat (Appian 21.2 and later)

Add the following properties inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.ajp.maxPacketSize=24576
```
```
conf.appserver.maxHeaderSize=65535
```
Note that the default value for the maxPacketSize is set to 8192 and for the maxHeaderSize, the max is 66536.
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 21.1)

Add the following property inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.maxHeaderSize=65535
```
Note The max value for maxHeaderSize is 66536.
Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 20.4 and earlier)

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: January 2025

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Ryan Good — Wed, 18 Sep 2024 15:55:15 GMT

Revision 22 posted to Appian Knowledge Base by Ryan Good on 9/18/2024 3:55:15 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat (Appian 21.2 and later)

Add the following properties inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.ajp.maxPacketSize=24576
```
```
conf.appserver.maxHeaderSize=65535
```
Note that the default value for the maxPacketSize is set to 8192 and for the maxHeaderSize, the max is 66536.
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 21.1 and earlier)

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: September 2024

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Ryan Good — Wed, 18 Sep 2024 15:42:33 GMT

Revision 21 posted to Appian Knowledge Base by Ryan Good on 9/18/2024 3:42:33 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat (Appian 21.2 and later)

Add the following properties inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.ajp.maxPacketSize=24576
```
```
conf.appserver.maxHeaderSize=65535
```
Note that the default value for the maxPacketSize is set to 8192 and for the maxHeaderSize, the max is 66536.
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 20.4 and earlier)

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

pauline.delacruz — Wed, 13 Mar 2024 20:17:11 GMT

Revision 20 posted to Appian Knowledge Base by pauline.delacruz on 3/13/2024 8:17:11 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat (Appian 21.1 and later)

Add the following properties inside the custom.properties file, located in <APPIAN_HOME>/conf.
```
conf.appserver.ajp.maxPacketSize=24576
```
```
conf.appserver.maxHeaderSize=65535
```
Note that the default value for the maxPacketSize is set to 8192 and for the maxHeaderSize, the max is 66536.
Restart the application server.

Note: Remember to update these configurations in custom.properties.<env> located inside <APPIAN_REPO>/conf/ for future deployments.

Tomcat (Appian 20.4 and earlier)

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: March 2024

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Nicholas Van Dyke — Wed, 10 Feb 2021 21:44:13 GMT

Revision 19 posted to Appian Knowledge Base by Nicholas Van Dyke on 2/10/2021 9:44:13 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Note: If any of the referenced tags are not present in the server.xml file, add them exactly as they are written in the above examples.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian Self-managed.

Last Reviewed: January 2021

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

James Lee — Fri, 10 Jul 2020 12:45:19 GMT

Revision 18 posted to Appian Knowledge Base by James Lee on 7/10/2020 12:45:19 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

... Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Symptom 4

The user experiences a HTTP 500 Error when navigating to: */suite/rest/a/applications/latest/app/design/monitoring:

The following entries are printed to the tomcat-stdOut.log:

com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation. java.lang.IllegalArgumentException: Header message of length [x] received but the packetSize is only [8,192]  at org.apache.coyote.ajp.AjpProcessor.readMessage(AjpProcessor.java:636)  at org.apache.coyote.ajp.AjpProcessor.receive(AjpProcessor.java:577)

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptoms 3 and 4

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Note: If any of the referenced tags are not present in the server.xml file, add them exactly as they are written in the above examples.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian Self-managed.

Last Reviewed: July 2020

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Rebecca Jonas — Wed, 17 Jun 2020 20:59:52 GMT

Revision 17 posted to Appian Knowledge Base by Rebecca Jonas on 6/17/2020 8:59:52 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP and HTTP protocol:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

Add the packetSize property to the AJP tag, the default is set to 8192 and the max is 65536. Add the maxHttpHeaderSize property to the HTTP tag, the max is 65536:

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>

<Connector port="9080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxHttpHeaderSize="65535"/>

Restart the application server.

Note: If any of the referenced tags are not present in the server.xml file, add them exactly as they are written in the above examples.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching the AJP value previously set in the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Additional Configurations if Using Apache as a Web Server

Add the following property LimitRequestFieldSize in the Apache httpd.conf file (Located in the <APACHE_Home>\conf) matching the HTTP value previously set in the server.xml file:

      LimitRequestFieldSize 65535

2. Restart Apache

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian On-Premise.

Last Reviewed: June 2020

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:52:48 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:52:48 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like one of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2019

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:52:16 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:52:16 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a generic error like on of the following:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

The System Has Encountered an Error. 
HTTP Code: 413
The system has encountered an error. Please try again later.

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2019

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:50:06 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:50:06 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Attempt to reproduce the issue while using the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still present, create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart the browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be output on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2019

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:39:57 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:39:57 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, the following error can be observed in the mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to the IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Test whether the issue if the issue can be reproduced while the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still reproduced please create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart your browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and the user is on Internet Explorer, continue with the following steps:

Select Tools > Select Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be outputted on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2019

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:38:00 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:38:00 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

To prevent this error from reoccurring, and to allow the requests to be fulfilled by the web server, we need to raise the maximum allowed size for the area of the message (header, body, etc) that is causing the error.

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Test whether the issue if the issue can be reproduced while the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still reproduced please create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart your browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and you are using Internet Explorer, continue with the following steps:

Select Tools > Select Developer Tools.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the Enter key.
The following should be outputted on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed:September 2019

Tags: email, web server, application server, 413, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Mon, 02 Sep 2019 05:35:47 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 9/2/2019 5:35:47 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

If Error Code 413 only occurs for one user please proceed with the following steps:

Test whether the issue if the issue can be reproduced while the browser's Private/Incognito mode.
1. If the issue cannot be reproduced in Private/Incognito mode, continue with step 2.
2. If it the issue is still reproduced please create a support case with Appian Support.
Clear the cache and all cookies on your browser using the instructions provided in the browser documentation.
Restart your browser and attempt to repeat the action that caused the 413 error.

If the steps above do not resolve the issue and you are using Internet Explorer, continue with the following steps:

Select Tools > Select 'Developer Tools'.
Select the Console tab.
Run the following string within the IE Dev Console: javascript:document.execCommand("ClearAuthenticationCache");
Press the 'Enter' key.
The following should be outputted on the console:

Affected Versions

This article applies to all versions of Appian.

Last Reviewed:September 2019

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Parmida Borhani — Tue, 13 Nov 2018 19:30:04 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2018 7:30:04 PM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart IIS.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 11:06:45 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 11:06:45 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 11:05:38 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 11:05:38 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>

<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 11:00:27 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 11:00:27 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>
<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
```
worker.ajp13w2.max_packet_size=24576
```
Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 10:57:16 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 10:57:16 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>
<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
```
worker.ajp13w1.max_packet_size=24576
```
worker.ajp13w2.max_packet_size=24576
Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 10:36:08 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 10:36:08 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>
<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
```
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
```
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
```
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:
worker.ajp13w1.max_packet_size=24576
worker.ajp13w2.max_packet_size=24576
Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure

KB-1161 "HTTP/1.1 413 Request Entity Too Large"/"Email body failed to render" errors thrown in application server log

Jordan Horwat — Mon, 12 Nov 2018 10:21:52 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 11/12/2018 10:21:52 AM

Symptoms

Users may experience one of the following symptoms:

Symptom 1

The HTTP File Upload Smart Service fails to upload files larger than 64KB (the threshold can be larger) with the following message in the application server log:

com.appian.integration.httpclient.smartnode.HttpFileUploadSmartNode - ConnectorRuntimeException [title=HTTP error connecting to ##URL##, com.appian.integration.core.exception.ConnectorRuntimeException: HTTP/1.1 413 Request Entity Too Large]

In the smart service’s output, an HTTP response code of 413 is returned.

Symptom 2

Appian auto-generated email alerts are not sent by the server with the following error in the application server log:

...
Caused by: java.io.IOException: Server returned HTTP response code: 414 for URL: XXXX
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/XXXX_emailHtml.jsp}

Symptom 3

When a specific user performs an action that works for other users, like clicking on a form, task or report, they receive a pink box error:

An internal error has occurred. The page could not be loaded. [HTTP Code = 413] (APNX-1-4279-001)

If using Apache, you will see the following error in mod_jk.log:

[error] ajp_marshal_into_msgb::jk_ajp_common.c (469): failed appending the header value” in the mod_jk log.

Cause

Action

For Symptoms 1 and 2

When the size of the request’s body is too large:

For IIS, the maxReceivedMessageSize parameter will have to be increased. By default, it is 64KB to prevent DOS attacks. For Apache, the parameter to be modified is LimitRequestBody.

For Symptom 3

When the size of the request’s header is too large:

JBoss

Add the following properties to the JBoss standalone.xml file under the <system-properties> tag:

<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="65535"/>
<property name="org.apache.coyote.ajp.MAX_PACKET_SIZE" value="65536"/>

Restart the application server.

Tomcat

Find the <connector> tag in the Tomcat server.xml file (Located in the directory <APPIAN_HOME>\tomcat\apache-tomcat\conf) for the AJP protocol:
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
Add the packetSize property to the tag, the default is set to 8192 and the max is 65536:
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" packetSize="24576"/>
Restart the application server.

Additional Configurations if Using IIS as a Web Server

Add the following property to your IIS workers.properties file (Located in the directory <ISAPI_HOME>\conf) matching value previously set to the server.xml file:

worker.ajp13w1.max_packet_size=24576
worker.ajp13w2.max_packet_size=24576

Restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: email, web server, application server, infrastructure