Receiving Messages From SIM Drop Off Topic After 30 Minustes (Doc ID 364281.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Integration Bus - Version 11.0 to 11.2 [Release 11]
Information in this document applies to any platform.
Checked for relevance 25-OCT-2010
Checked for relevance 12-Oct-2012


Symptoms

When shutting down the e*Ways (e.g. for a batch job or db backup), Store Inventory Management (SIM) will still publish to the Java Message Service (JMS). When this happens, sometimes the published message is lost, and must be copied from the publishing component log and re-processed after everything is back up.

Loss of data and/or productive time to recover lost data.

During the investigation of this issue, several Rib Diagnostic and Monitoring Toolkit (RDMT) scripts were enhanced or added, and provided to the customer. One of these scripts uses stcmsctrlutil to gather a report of message statistics (msgstats). A small sample of its output is included immediately below...

Message[8]:
Message.SeqNo=4867
Message.Size=3601
Message.EnqueueTime=1143199949135
Message.JMSProperty.DM=1
Message.JMSProperty.DN=etDSDReceipt
Message.JMSProperty.EX=1800000
Message.JMSProperty.MI=ID:fcff6e0:10a2af9d389:eb3a:a4e2ba69:10a2c037010
Message.JMSProperty.PR=4
Message.JMSProperty.RD=False
Message.JMSProperty.TS=1143199723536
Message.UserProperty.threadValue=1

Cause

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