we are having problems getting our taskException emails to render after upgrade

In the application server adjust these settings in custom.properties to point to the app server

conf.suite.MAIL_SCHEME=http
conf.suite.MAIL_SERVER_AND_PORT=localhost:8080

this will basically tell JBoss to grab the JSP from itself without going through the web server (which is not required since it's a dynamic request which should be served by the app server anyway)

thanks Eduardo you are the best!

My pleasure Nate!

after making these changes we got a new exception:

2014-07-22 05:51:08,378 [default-threads - 36] ERROR com.appiancorp.ra.workpoller.WorkItemListener - The following exception occurred while attempting to complete work item [(WorkId: 115, WorkType: [AbstractMailRequest: from=null, to=kevinge@amazon.com, namoor@amazon.com, satishkr@amazon.com, subject=Alert: Error in Task of Process.], Response: null, ServerName: NotificationsEmail)] - Exception:
javax.resource.spi.work.WorkCompletedException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:224)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:849)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: javax.ejb.EJBException: com.appiancorp.process.engine.EmailBodyException: Email body failed to render
at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:78)
at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:92)
at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:107)
at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:56)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:203)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

In that stack trace there should be several "Caused by" clauses. The first one is very generic: "Email body failed to render" can you paste here only the next "Caused by" clauses? It could be your server doesn't know what localhost means (hosts file misconfiguration), let's have a look.

we just realized that our build from env.properties file changes did not make it into the custom.properties file... the conf.suite.MAIL_SCHEME was still commented out and did not take the token from the build file.

Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

Caused by: java.io.EOFException: SSL peer shut down incorrectly

Oh then that's why. Once these settings make it to the custom.properties the issue will be resolved.

it made it to the custom properties... however the notification settings did not make it on first migration boot... we had this:
server.conf.notifications.threads_new_msg_timing=never
server.conf.notifications.threads_invite_msg_timing=never
server.conf.notifications.threads_accept_invite_msg_timing=never
server.conf.notifications.threads_decline_invite_msg_timing=never
server.conf.notifications.send_thread_msg_timing=never
server.conf.notifications.group_membership_requested_timing=never
server.conf.notifications.group_invitation_timing=never
server.conf.notifications.group_membership_removed_timing=never
server.conf.notifications.group_membership_request_approved_timing=never
server.conf.notifications.group_membership_request_rejected_timing=never
server.conf.notifications.group_invitation_accepted_timing=never
server.conf.notifications.group_invitation_declined_timing=never
server.conf.notifications.send_link_msg_timing=never
server.conf.notifications.send_feedback_msg_timing=never
server.conf.notifications.page_approved_msg_timing=never
server.conf.notifications.system_msg_timing=never
server.conf.notifications.page_approval_req_msg_timing=never
server.conf.notifications.collab_send_link_msg_timing=never
server.conf.notifications.collab_access_approved_msg_timing=never
server.conf.notifications.collab_access_rejected_msg_timing=never
server.conf.notifications.collab_access_request_msg_timing=never
server.conf.notifications.collab_approved_changes_msg_timing=never
server.conf.notifications.collab_rejected_changes_msg_timing=never
server.conf.notifications.collab_change_request_msg_timing=never
server.conf.notifications.collab_expiring_files_msg_timing=never
server.conf.notifications.collab_invite_kc_msg_timing=never
server.conf.notifications.collab_accept_invite_msg_timing=never
server.conf.notifications.collab_decline_invite_msg_timing=never
server.conf.notifications.th_task_created_timing=never
server.conf.notifications.th_bug_created_timing=never
server.conf.notifications.th_bug_status_changed_timing=never
server.conf.notifications.process_escalation_msg_timing=never
server.conf.notifications.process_sub_link_republished_timing=never
server.conf.notifications.process_super_process_causes_publishing_timing=never
server.conf.notifications.process_sub_link_disabled_deleted=never
server.conf.notifications.process_new_task_me_timing=never
server.conf.notifications.process_new_task_others_timing=never
server.conf.notifications.process_cannot_delete_cancel_sub=never
server.conf.notifications.process_exception_msg_timing=never
server.conf.notifications.task_exception_msg_timing=never

Is there anyway to put this back for all users?

we see there is this plugin for resetting notifications...
Portal_Utilities_3.0.0(1) but it only runs on one user at a time and for only one setting.