Messages Flow Stuck after SOA Servers Crashes and Restarted (Doc ID 1943457.1)

Last updated on AUGUST 23, 2024

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal

In the event of a SOA server crash/catastrophic event, the healthcare engine
sequencing modules may result in an undermined state. Even though there are
no messages lost, the messages are not flowing because the sequencing module
does not recognize the undermined state for continual processing.

What is the best approach to get messages flowing again?

Solution

	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

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Messages Flow Stuck after SOA Servers Crashes and Restarted (Doc ID 1943457.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!