My Oracle Support Banner

Starting OIM on DR site fails with: Could not register a DisconnectListener (Doc ID 2142436.1)

Last updated on MARCH 05, 2018

Applies to:

Identity Manager - Version and later
Information in this document applies to any platform.


On : version, Infrastructure

Starting one of the OIM nodes after changing the listen address to use the local hosts file alias, leads to errors and the managed server does not come up.

May 20, 2016 12:08:34 PM EDT>

There are 1 nested errors:

weblogic.rmi.extensions.DisconnectMonitorUnavailableException: Could not register a DisconnectListener for [null]
  at weblogic.rmi.extensions.DisconnectMonitorListImpl.addDisconnectListener(
  at weblogic.server.AdminServerListenerService.initializeAdminServerListener(
  at weblogic.server.AdminServerListenerService.start(


The issue can be reproduced at will with the following steps:
1. Have the Disaster Recover (DR) site cluster nodes up and running fine.
2. Edit /etc/hosts on the OIM physical host and add an entry for the VIP IP address and hostname
3. Change the listen address for oim_server1 managed server to use the name from #2 above
4. Start that OIM node and it will fail with the above errors


Change the listen address for the managed server to use the name listed in the local hosts file which represents the VIP address on the host machine. 


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.