Siebel Gateway Cluster Is Not Accessible When All But One Node Goes Down
(Doc ID 2755026.1)
Last updated on FEBRUARY 25, 2021
Applies to:
Siebel CRM - Version 20.6 and laterInformation in this document applies to any platform.
Symptoms
Siebel 20.6 version
The following tests were executed, in order to better understand the Gateway Cluster behaviors:
GW - Gateway
Test case 1 - GW1- Running, GW2- Running, GW3- down (Result: all good-> new connections, existing connected users and integrations remain)
Test Case 2 - GW1 -Running, GW2-Down, GW3 - Running (Result: all good-> new connections, existing connected users and integrations remain)
Test Case3 - GW1 -Down, GW2 - Down, GW3 -Running (Result: all failed-> new connections, existing connected users and integrations, all down)
Steps executed by customer:
-------------------------------
1. Set up a Siebel environment with Gateways clustered running with 3 nodes .
2. Test a few variations putting one of the gateway nodes down or 2 and verify the behavior.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |