Need and Implement Error JMS Queue

Problem Statement
In Oracle Fusion(SOA, OSB, ODI) assuming a scenario when a customized service is transforming a web service, file-based or any other form of the message and send it to Edge application via JMS Queue and the content of the message is not acceptable by the Edge application. It could result in below outcomes:
• A message with incorrect content/data starts spinning in admin Weblogic console and remain in Message Pending of JMS Queue
• If we allow the message to spin, then it leads to an increase in error logs in Edge Application which eventually fills up the storage
• Gradually after filling up the storage of edge application then may cause the edge application servers to crash and go in shutdown state


Workaround
Delete this unwanted spinning message from the JMS Queue.
If one is unable to delete the message from the JMS Queue, then pause the JMS queue and let the message go into Message Current from Message Pending


Permanent Solution
On Weblogic admin console of Fusion, for each such customizes JMS Queue create a corresponding error JMS queue.
Once those error JMS queue is created then

  1. Go to JMS Module
  2. Click on
  3. Click on actual JMS Queue where the message is spinning
  4. Click on Delivery Failure tab
  5. Click on Lock and Edit (on the left-hand side under Change Center)
  6. Amend Redelivery Delay Override to the desired value like 5 (This is in milliseconds and retries the same message after the set value)
  7. Amend Redelivery Limit to the desired value like 5 (Number of retries attempted)
  8. Amend Expiration Policy to Redirect (This moves the above-unwanted message post number of retries to an Error Destination)
  9. Amend Error Destination to Error JMS Queue Name

Benefits
• Restriction on number of attempts of incorrect message
• Unwanted messages are no longer spinning in Weblogic admin server of Fusion
• Reduce the probability of filling up of storage as there is a reduction in error logging of edge application
• Edge application servers remain healthy and up and running

Join the Conversation

  1. humourme89's avatar
  2. anomaly1984's avatar
  3. Unknown's avatar
  4. skerry04's avatar
  5. Pinky Sachdev's avatar
  6. ishank05's avatar

23 Comments

Leave a comment

Design a site like this with WordPress.com
Get started