Paused Healthcare (HC) endpoints become active after a managed server restart
Last updated on APRIL 12, 2016
Applies to:Oracle SOA Suite - Version 18.104.22.168.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
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