Email and Inbox Notifications Are Not Working in WebLogic Clustered Environment Due to Missing JMS Server Target, JMS Log Shows, "Exception occured while sending message to queue:com.agile.notification.email.queue"
(Doc ID 1210586.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Agile PLM Framework - Version 184.108.40.206 and later
Oracle Agile Product Collaboration - Version 220.127.116.11 and later
Information in this document applies to any platform.
When attempting to send an Inbox or Email Notifications, the following error occurs:
Error Message in JMS Log:
[17 Sep 2010 20:28:54, EDT] [ERROR] [ <JMS Message Sender> Exception occured while sending message to queue:com.agile.notification.email.queue Reason : While trying to lookup 'com.agile.notification.email.queue' didn't find subcontext 'notification'. Resolved 'com.agile']
[17 Sep 2010 20:28:54, EDT] [ERROR] [ <JMS Message Sender> Exception occured while sending message to topic: sync_topic Reason : Unable to resolve 'sync_topic'. Resolved '']
Error in std.err file:
javax.naming.NameNotFoundException: While trying to lookup 'com.agile.notification.email.queue' didn't find subcontext 'notification'. Resolved 'com.agile'; remaining name 'notification/email/queue'
Workflow notifications, as well a Send action notifications are affected.
The issue can be reproduced at will with the following steps:
1. In Java Client Admin, Open Part Send Notification template | Configure to send both EMail & Inbox Notification
2. Open a Part Object | Send it to a User | Wait till Notification Wait time completes
3. Observe that Users did not receive any Email or Inbox Notification
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Configuring a Standalone JMS|
|Configuring a Distributed JMS Cluster (Recommended)|