Unstable Cluster Using Unicast Cluster Communication in OCSG Domain
(Doc ID 1475374.1)
Last updated on NOVEMBER 09, 2017
Applies to:Oracle Communications Services Gatekeeper - Version 5.0.0 to 5.0.0 [Release 5.0]
Information in this document applies to any platform.
When using Unicast cluster communication, both AT and NT clusters are not stable. Below logs are seen:
<WLNG_AT3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default
jvmid:-1075015999180473833S:OCSGDOMAIN:WLNG_AT2 from cluster view due to timeout.>
<Info> <Cluster> <BEA-000112> <unknown>
jvmid:4915393240391668892S:OCSGDOMAIN:WLNG_NT2 from cluster view due to timeout.>
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