Paused Healthcare (HC) endpoints become active after a managed server restart
(Doc ID 2125059.1)
Last updated on MARCH 04, 2019
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Paused Healthcare (HC) endpoints become active after a managed server restart, without user resuming endpoints.
HC endpoint starts to accept incoming messages, however cannot publish to JMS queues as they are not yet available.
This causes the message flow to get stuck as messages go into the b2b_sequence_manager table with null values for columns: message_id, app_message_id, wire_message_id
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