Both Managed Servers in Active State at Same Time after Full GC Exceeds Heartbeat Timeout (Doc ID 2170005.1)

Last updated on MARCH 03, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 to 12.1.3.0.0 [Release 11gR1 to 12c]
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.0 version, Health Care FastPath

ACTUAL BEHAVIOR
---------------
When a manually triggered full garbage collection on managed server MS01 (passive) takes over 100 seconds, this forces a switch from server MS02 (active) to MS01. Yet after garbage collection completes the source endpoints are no longer receiving messages.

B2B_HA_REGISTRY table still shows that MS02 is ACTIVE but logs suggests that the active server has become MS01.

EXPECTED BEHAVIOR
-----------------------
The active managed server should not be switched to passive since the missed heartbeat actually occurred on the passive managed server.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run full garbage collection on MS01 that takes longer than the heartbeat timeout.
2. Active state switches to MS01.

Cause

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