Limbo Messages Are Not Processed By Failure Port When Their Maximum Retries Have Been Reached
Last updated on MAY 11, 2016
Applies to:Oracle Commerce Platform - Version 9.0 and later
Information in this document applies to any platform.
The Redelivery Manager stores a different value for redelivery than the DMS_LIMBO_MSG delivery_count value such that on startup the count is reset.
The RedeliveryManager on the MessageLimbo class is not re-initialised with the correct data on start up. Subsequently the in memory count (stored in the RedeliveryManager) for each message is reset on start-up, resulting in the in-memory count containing a different value to the DELIVERY_COUNT stored on DMS_LIMBO_MSG table, this in turn creates a code condition where the messages are not passed to their redelivery port.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms