One RIB-APP Failure Messages are Getting Retried by a Different RIB-APP Adapters Incorrectly and Shutting Them Down
(Doc ID 2899973.1)
Last updated on OCTOBER 03, 2022
Applies to:Oracle Retail Integration Cloud Service - Version NA and later
Information in this document applies to any platform.
Adapters are going down with below error:
2022-04-12 10:19:51,006 ERROR [Items_sub_1] j2ee.RIBMessageSubscriberEjb (RIBMessageSubscriberEjb.java:753) - =============Root Cause Begin====================
2022-04-12 10:19:51,007 ERROR [Items_sub_1] j2ee.RIBMessageSubscriberEjb (RIBMessageSubscriberEjb.java:756) - Message #xxxxxx missing from hospital database
java.lang.IllegalStateException: Message #xxxxxx missing from hospital database
at java.lang.Thread.run(Thread.java:750) [?:1.8.0_321]
2022-04-12 10:19:51,008 ERROR [Items_sub_1] j2ee.RIBMessageSubscriberEjb (RIBMessageSubscriberEjb.java:760) - =============Root Cause End====================
- MFCS had triggered some Item family messages which failed in RIB-OCDS Error Hospital against rib-ocds.Item_Subscriber adapter with some business errors. This is expected.
- Those failed messages were somehow getting retried by the RIB-EXT component and given to rib-ext.Item_Subscriber adapter. After the retry the messages are attempted to get updated in RIB-EXT Error hospital where the corresponding records do not exists. Thus those problematic messages end up failing with above error and causing the rib-ext.Item_Subscriber adapter to go down.
- Note that these messages belong to rib-ocds error hospital and should not given to rib-ext at-all. Here both rib-ext.Item_Subscriber and rib-ocds.Item_Subscriber adapters share the same topic 'etItemsFromRMS'.
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