Last updated on MAY 31, 2016

Applies to:

Symptoms

On : 11.1.2.2.0 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.


ERROR
-----------------------
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(DisconnectMonitorListImpl.java:83)
  at weblogic.security.utils.AdminServerListener.startDisconnectListener(AdminServerListener.java:118)
  at weblogic.security.utils.AdminServerListener.startListening(AdminServerListener.java:100)
  at weblogic.security.utils.AdminServerListener.start(AdminServerListener.java:73)
  at weblogic.server.AdminServerListenerService.initializeAdminServerListener(AdminServerListenerService.java:31)
  at weblogic.server.AdminServerListenerService.start(AdminServerListenerService.java:24)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

>





STEPS
-----------------------
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

Changes

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. 

Cause