Workflow emails are not getting triggered and we are getting error as below mentioned. We cross checked the run modes as well and it is pointing to correct one only. Not able to figure it out what is cause of the issue.
Here is the error log:
*ERROR* [EMailNotificationService-Processor] com.day.cq.workflow.impl.email.EMailNotificationService Error while sending email.
at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:308) [com.day.cq.cq-commons:5.11.14]
at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:299) [com.day.cq.cq-commons:5.11.14]
at com.day.cq.workflow.impl.email.EMailNotificationService.getHostPrefix(EMailNotificationService.java:426) [com.day.cq.workflow.cq-workflow-impl:6.2.12]
at com.day.cq.workflow.impl.email.NotificationImpl.load(NotificationImpl.java:184) [com.day.cq.workflow.cq-workflow-impl:6.2.12]
at com.day.cq.workflow.impl.email.EMailNotificationService.sendNotification(EMailNotificationService.java:262) [com.day.cq.workflow.cq-workflow-impl:6.2.12]
at com.day.cq.workflow.impl.email.EMailNotificationService$EventProcessor.run(EMailNotificationService.java:542) [com.day.cq.workflow.cq-workflow-impl:6.2.12]
at java.lang.Thread.run(Thread.java:748)
Any idea on what would be the problem?
Solved! Go to Solution.
Hi sai,
I don't see any config name as "local", you should have local config value. Did you try adding "local" and test?
In externalizer, the config name "local" is hardcoded, so you need to have local regardless you are using it or not.
Ex:
return externalLink(null, "local", scheme, path);
However, externalizer is multifield, you can add one more config as "local". Please add the local and check.
Thanks!
Go to <server>/system/console/configMgr and locate Link Externalizer and add value for "local"
Hope this helps!.
Thanks!
Hi GaneshM-
Thank you for the response. We have externalizer configurations to a specific environments based on run-mode value. And when I checked again it is reflecting all author and publisher specific urls that we have configured. As this issue is happening at environment level, it should not be local. But we trigger a workflow it is failing with the exception, which I mentioned above.
-Sai
Views
Replies
Total Likes
Hi Sai,
Did your "local" field empty in Externalizer? in "EMail Notification Service" its mentioned that "Deprecated - Use the 'Link Externalizer' service to configure the host prefix (host.prefix)"
The Notification Email uses the "local" config value for host in Email Notification Service
FYI, I made the local value empty and trigged workflow got the same exception
Exception
java.lang.IllegalArgumentException: Could not find configuration for domain 'local'
at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:308)
at com.day.cq.commons.impl.ExternalizerImpl.externalLink(ExternalizerImpl.java:299)
at com.day.cq.workflow.impl.email.EMailNotificationService.getHostPrefix(EMailNotificationService.java:417)
at com.day.cq.workflow.impl.email.NotificationImpl.load(NotificationImpl.java:180)
at com.day.cq.workflow.impl.email.EMailNotificationService.sendNotification(EMailNotificationService.java:253)
at com.day.cq.workflow.impl.email.EMailNotificationService$EventProcessor.run(EMailNotificationService.java:512)
Can you make the field with some host name and try?
Thanks!
Views
Replies
Total Likes
Hi GaneshM - We alredy the runmode configuration to fill the domain value. We are maintaining author, publisher and pdf urls for domains field of Link Externalizer. I cross checked and it still it didn't helped us.
Views
Replies
Total Likes
To send an email in a workflow - you can write a custom step and use the MesssageGateWay service - whcih works perfect: Adobe Experience Manager Help | Creating an Adobe Experience Manager 6.4 custom workflow step that u...
Views
Replies
Total Likes
Can you share the screenshot of externalizer?
Thanks!
Views
Replies
Total Likes
Hi GaneshM-
PFA.
Views
Replies
Total Likes
Hi sai,
I don't see any config name as "local", you should have local config value. Did you try adding "local" and test?
In externalizer, the config name "local" is hardcoded, so you need to have local regardless you are using it or not.
Ex:
return externalLink(null, "local", scheme, path);
However, externalizer is multifield, you can add one more config as "local". Please add the local and check.
Thanks!
Above resolve the issue. Thank you GaneshM for the help.
Views
Replies
Total Likes
Views
Likes
Replies