JMS Messages Driven Into Limbo by SQL Errors
Last updated on JANUARY 10, 2017
Applies to:Oracle Commerce Platform - Version 10.0 and later
Information in this document applies to any platform.
Application processing that is normally driven by JMS-based events becomes throttled and the number of rows in the DMS_LIMBO_MSG table begins to grow.
Application server logging shows database errors in the nature of "value too large for column" (ORA-12899, on an Oracle database) that names a SQL table used by the Oracle Commerce JMS impelementation: SQLDMS. The table named in the errors is DMS_MSG_PROPERTIES. It is the value column that lacks sufficient storage. The name of the property in the failed INSERT operation is "singularityheader".
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