Message Doesn't Retry About It Changes To MSG_WAIT_STACK
(Doc ID 1639089.1)
Last updated on JANUARY 21, 2020
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Technology Adapters
An end-to-end interfaces has been completed. This interface receives HL7 message via MLLP protocol through Oracle Healthcare Adapter. It then submits the message to an inbound JMS Queue. Then a composite receives this message and sends to an outbound JMS Queue. From the outbound JMS the message then goes to outbould Healthcare Adapter and is sent to an external application via MLLP.
When the outbound external application is down, then the state of the message changes to "MSG_WAIT_TRANSMIT". The message remains in this state for about 30 seconds and if the external application come back up then the waiting message is sent across. But if it waits longer then the message state changes to MSG_WAIT_STACK. Once the state changes to MSG_WAIT_STACK then the message never retries and as a result the message never recovers itself.
We need to make sure that the MSG_WAIT_TRANSMIT must be for indefinite time, so that as soon as the external application is started, all the messages, should automatically start sending.
The issue can be reproduced at will with the following steps:
1. Stop the outbound external application.
2. The message never retries and as a result the message never recovers itself.
The issue has the following business impact:
The message never retries and as a result the message never recovers itself.
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