KB-2052 System emails/process emails are no longer being sent with a "Connection refused" error

Maggie Deppe-Walker — Tue, 23 Aug 2022 14:42:42 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 8/23/2022 2:42:42 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.
The application server log will contain one of the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

ERROR com.appiancorp.process.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [[WorkId: 247, EngineId: notifications-email, Request: MailRequest:null as null by null, Response: null]] - Exception: 
javax.resource.spi.work.WorkCompletedException: java.lang.RuntimeException: Could not prepare email for: CompatibleEmailRecipients{locale=en_US, timeZone=IST, calendarId=gregorian, startPage=https://example-startpage.com/suite/tempo, emailAddresses=[a****.com]}
	at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:242)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Could not prepare email for: CompatibleEmailRecipients{locale=en_US, timeZone=IST, calendarId=gregorian, startPage=https://example-startpage.com/suite/tempo, emailAddresses=[a*****.com]}
...
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/taskException_emailHtml.jsp}
...
Caused by: java.net.SocketException: Unexpected end of file from server

Cause

This issue occurs when the application server is unable to connect to the HTTP endpoint to render the email body. This can occur when there is a mis-configuration in custom.properties or if the HTTP listener has been removed from the application server configuration.

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See the documentation for more details.
Confirm that the standalone.xml (JBoss) and context.xml (Tomcat) configurations have declared the appropriate HTTP listener in order to accept HTTP connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2022

Tags: administration, email, application server, infrastructure

KB-2052 System emails/process emails are no longer being sent with a "Connection refused" error

Maggie Deppe-Walker — Thu, 21 Jul 2022 17:43:11 GMT

Revision 10 posted to Appian Knowledge Base by Maggie Deppe-Walker on 7/21/2022 5:43:11 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.
The application server log will contain one of the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused


ERROR com.appiancorp.process.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [[WorkId: 247, EngineId: notifications-email, Request: MailRequest:null as null by null, Response: null]] - Exception: 
javax.resource.spi.work.WorkCompletedException: java.lang.RuntimeException: Could not prepare email for: CompatibleEmailRecipients{locale=en_US, timeZone=IST, calendarId=gregorian, startPage=https://example-startpage.com/suite/tempo, emailAddresses=[a****.com]}
	at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:242)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Could not prepare email for: CompatibleEmailRecipients{locale=en_US, timeZone=IST, calendarId=gregorian, startPage=https://example-startpage.com/suite/tempo, emailAddresses=[a*****.com]}
...
Caused by: com.appiancorp.process.engine.EmailBodyException: Email body failed to render: MailBody{filename=/ntf/emailHtml/taskException_emailHtml.jsp}
...
Caused by: java.net.SocketException: Unexpected end of file from server

Cause

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See the documentation for more details.
Confirm that the standalone.xml (JBoss) and context.xml (Tomcat) configurations have declared the appropriate HTTP listener in order to accept HTTP connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2022

Tags: administration, email, application server, infrastructure

KB-2052 System emails/process emails are no longer being sent with a "Connection refused" error

Parmida Borhani — Thu, 09 Jan 2020 23:53:55 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 1/9/2020 11:53:55 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See the documentation for more details.
Confirm that the standalone.xml (JBoss) and context.xml (Tomcat) configurations have declared the appropriate HTTP listener in order to accept HTTP connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-2052 System emails/process emails are no longer being sent with a "Connection refused" error

Parmida Borhani — Thu, 09 Jan 2020 23:53:13 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 1/9/2020 11:53:13 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See the documentation for more details.
Confirm that the standalone.xml (JBoss) and context.xml (Tomcat) configurations have declared the appropriate HTTP listener in order to accept HTTP connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Parmida Borhani — Thu, 09 Jan 2020 23:52:34 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 1/9/2020 11:52:34 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See the documentation for more details.
Confirm that the standalone.xml (JBoss) and context.xml (Tomcat) configurations have declared the appropriate HTTP listener in order to accept HTTP connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tom Ryan — Thu, 09 Jan 2020 02:26:55 GMT

Revision 6 posted to Appian Knowledge Base by Tom Ryan on 1/9/2020 2:26:55 AM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

This issue occurs when the application server is unable to connect to the HTTP endpoint to render the email body. This can occur when: a) There is a mis-configuration in {{custom.properties}}, or b) the HTTP listener has been removed from the application server configuration.

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See here for more details.
Confirm that the standalone.xml (JBoss) and Context.xml (Tomcat) configurations have declared the appropriate http listener in order to accept http connections.
Use a networking utility to confirm connectivity to the configured HTTP endpoint.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tristan Newmann — Thu, 09 Jan 2020 00:20:00 GMT

Revision 5 posted to Appian Knowledge Base by Tristan Newmann on 1/9/2020 12:20:00 AM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See here for more details.
Confirm that the standalone.xml (JBoss) and Context.xml (Tomcat) configurations have declared the appropriate http listener in order to accept http connections.
Use a networking utility to confirm connectivity to the application server on the expected port.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tristan Newmann — Mon, 06 Jan 2020 23:01:36 GMT

Revision 4 posted to Appian Knowledge Base by Tristan Newmann on 1/6/2020 11:01:36 PM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

The underlying cause of the issue can vary, but is usually associated with web server or application server configurations, or networking configurations.

The application server exposes and invokes an HTTP endpoint in order to generate the email body. When the application server is unable to invoke the endpoint (due to a configuration or networking issue), it will be unable to generate email bodies, and thus unable to send emails.

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME. See here for more details.
Confirm that the standalone.xml (JBoss) and Context.xml (Tomcat) configurations have declared the appropriate http listener in order to accept http connections.
Use a networking utility to confirm connectivity to the application server on the expected port.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tristan Newmann — Mon, 06 Jan 2020 05:33:20 GMT

Revision 3 posted to Appian Knowledge Base by Tristan Newmann on 1/6/2020 5:33:20 AM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

The underlying cause of the issue can vary, but is usually associated with web server or application server configurations, or networking configurations.

Action

Use the telnet utility to attempt to access the value declared custom.properties for the MAIL_SERVER_AND_PORT configuration to verify network connectivity
Use the netstat utility to ensure that the port is being listened to by the expected OS process associated with the application server
Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME.
Confirm that the standalone.xml (JBoss) and Context.xml (Tomcat) configurations have declared the appropriate http listener in order to accept http connections.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tristan Newmann — Mon, 06 Jan 2020 00:27:22 GMT

Revision 2 posted to Appian Knowledge Base by Tristan Newmann on 1/6/2020 12:27:22 AM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

In order for the application server to send an email, it exposes a HTTP endpoint that it itself invokes in order to generate the email body that will be used in the sent email. When the app server is unable to invoke the endpoint (due to a configuration or networking issue), it will be unable to generate email bodies, and thus unable to send emails.

The underlying cause of the issue can vary, but is usually associated with web server or application server configurations, or networking configurations.

Troubleshooting

Use the telnet utility to attempt to access the value declared custom.properties for the MAIL_SERVER_AND_PORT configuration to verify network connectivity
Use the netstat utility to ensure that the port is being listened to by the expected OS process associated with the application server

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME.
Confirm that the standalone.xml and Context.xml configurations have declared the appropriate http/https listener in order to accept http connections.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: administration, email, application server, infrastructure

KB-XXXX System emails/process emails are no longer being sent with a "Connection refused" error

Tristan Newmann — Mon, 06 Jan 2020 00:26:32 GMT

Revision 1 posted to Appian Knowledge Base by Tristan Newmann on 1/6/2020 12:26:32 AM

Symptoms

System emails for account creation are not sent.
System emails for resetting a password are not sent.
Process models with Send Email nodes are paused.

The application server log will contain the following errors:

ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 14, WorkType: [AbstractMailRequest: from=null, to=<Email>, subject=<Subject>], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
…
Caused by: javax.net.ConnectException: Connection Refused

Cause

The underlying cause of the issue can vary, but is usually associated with web server or application server configurations, or networking configurations.

Troubleshooting

Use the telnet utility to attempt to access the value declared custom.properties for the MAIL_SERVER_AND_PORT configuration to verify network connectivity
Use the netstat utility to ensure that the port is being listened to by the expected OS process associated with the application server

Action

Confirm that <APPIAN_HOME>/conf/custom.properties has the correct and expected configurations for MAIL_SERVER_AND_PORT and MAIL_SCHEME.
Confirm that the standalone.xml and Context.xml configurations have declared the appropriate http/https listener in order to accept http connections.

Tags: administration, email, application server, infrastructure