My Oracle Support Banner

One NT Server Abruptly Shuts Down While The Other NT Server Coming Up (Doc ID 973333.1)

Last updated on MARCH 29, 2018

Applies to:

Oracle Communications Services Gatekeeper - Version: 4.1.0 and later   [Release: 4.1 and later ]
Information in this document applies to any platform.


The Scenario is as follow:
  • Both NT servers are up and running with only one network card
  • Database is on a separate remote server and is up and running
  • Remove the NT1 network interface
  • Send requests on NT2 machine that is running fine
  • Restart NT1
  • When NT2 see that NT1 is back, NT2 goes shutdown

    The following errors are seen on the NT2 server logs:
    ####<Nov 22, 2009 4:01:04 PM GMT+05:30> <Notice> <WLSS.ReplicatedStore> <gnnsdp24> <WLNG_NT2> <Timer-13> <> <> <> <1258885864988> <BEA-332028> <Successfully joined partition; using replica WLNG_NT1 as sponsor>
    ####<Nov 22, 2009 4:01:05 PM GMT+05:30> <Alert> <WLSS.ReplicatedStore> <gnnsdp24> <WLNG_NT2> <SIP Replication Timer Thread> <> <> <> <1258885865051> <BEA-332105> <Replica WLNG_NT2 claims client is not registered>
    ####<Nov 22, 2009 4:01:05 PM GMT+05:30> <Emergency> <WLSS.Engine> <gnnsdp24> <WLNG_NT2> <SIP Replication Timer Thread> <> <> <> <1258885865055> <BEA-330095> <Fatal error at runtime, gracefully shutting down>




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

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