Some Messages Failing With Error "JAVA.LANG.ILLEGALSTATEEXCEPTION: MESSAGE #XXXX MISSING FROM HOSPITAL" Are Blocking Other Messages From Flowing Through RIB
(Doc ID 1066566.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Retail Integration Bus - Version 12.0.1 and later
Information in this document applies to any platform.
Checked for relevance on 29-Sep-2011
Checked for relevance on 24- May - 2018
Some messages failing with error : java.lang.IllegalStateException: Message #XXXX missing from hospital are blocking the flow of all messages through RIB.
- Message #16280 missing from hospital database
Incoming message is marked as being in hospital as message number:
16280, but the row is missing from the hospital database. This is a
serious internal inconsistency in the hospital, which you will need to
resolve manually. There are several known causes for it:
 Somebody manually deleted rows from rib_message. (Don't do that!! Set delete_pending to 1 instead.)
 Somebody set in_queue to 0 while the message was still in the queue, then set delete_pending to 1.
Retry events for two different schemas with different hospitals are
getting mixed up because their JMS Connection Points are pointing to
the same IQ Manager. (Open the config for your JMS CP and check the
host/port. Is it pointing to the right IQ Manager on the right machine?
How about the hospital DB CP?)
 You have renamed the collab or
created a new one in such a way as to confuse SeeBeyond's JMS
implementation into sending you retry messages from the past.
In any of these cases, you'll have to manually remove this message from the JMS queue.
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