My Oracle Support Banner

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

Last updated on AUGUST 09, 2018

Applies to:

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


On : version, Health Care FastPath

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.

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

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.


To view full details, 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 a vibrant support community of peers and Oracle experts.