WF-Mailer Fails to Send Email Notifications after cloning

最新推荐文章于 2025-04-14 18:00:31 发布

转载最新推荐文章于 2025-04-14 18:00:31 发布 · 1.1k 阅读

文章标签：

#WF

WF 专栏收录该内容

14 篇文章

订阅专栏

在克隆后，尽管所有代理监听器和通知邮件器都已经启动运行，但邮件并未正常流转。通过检查日志文件发现，邮件器在尝试获取HTML内容时遇到连接拒绝错误。经过调查，发现克隆过程中源实例被带下进行冷备份时，一些工作流程处于队列中，并可能使用了源实例的Web服务器地址。因此，在克隆后，邮件器仍然尝试使用旧URL导致连接失败。解决方案是清空并重新填充WF_NOTIFICATION_OUT队列。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

转自：http://mtalmasri.blogspot.tw/2012/08/mailer-fails-to-send-email.html

After cloning, mails were not floating through workflow mailer although all agent listener and notification mailer was up and running.

Issue:-
After some time we checked latest mailer log FNDCPGSCXXXXX.txt at $APPLCSF/$APPLLOG.
Below error was their in logs:-
'Problem obtaining the HTML content oracle.apps.fnd.wf.common.HTTPClientException: Unable to invoke method HTTPClient.HTTPConnection.Get caused by: java.net.ConnectException: Connection refused'

Investigation:-
what i got to know after bit of investigation is at the time we brought down source instance for cold back up, some of the workflows were in queue and they might be using source instance webserver address. After clone Since the mailer still had some events with the old url in the queue, the mailer fails with connection refused error and goes down after 10 attempts.

Solution:-
Solution is to purge the wf_notification_out outbound message queue and repopulates from the WF_NOTIFICATION table.

PFB complete solution:-

1. Stop the Workflow mailer.

2. Purge the wf_notification_out queue and recreate it out of the wf_notifications table by executing:
cd $FND_TOP/patch/115/sql
sqlplus APPS/ @wfntfqup.sql APPS APPLSYS

3. Start the mailer

4. Retest the issue by submitting the same workflow again.