When recycling a Control-M/Enterprise (EM) component such as the GUI Server in the Control-M Configuration Manager (CCM), the Naming Service component can go into a Hanging or Down state. This occurs randomly but usually after a few consecutive recycles of the GUI Server from the CCM. Naming Service debug logs showed below messages: +++ 2017-09-18 17:14:43.169@LM_DEBUG@TAO (5896|5660) - IIOP_Transport[276]::recv, read failure - connection reset errno 10054 2017-09-18 17:14:43.169@LM_ERROR@TAO (5896|5660) - Transport[276]::handle_input, error parsing incoming message 2017-09-18 17:14:43.169@LM_DEBUG@TAO (5896|5660) - Resume_Handle::handle_input_return_value_hook, handle_input returning -1, so handle is not resumed. 2017-09-18 17:14:43.169@LM_DEBUG@TAO (5896|5660) - Connection_Handler[276]::handle_input_internal, handle = 276/276, retval = -1 +++ When this happens, there is an error "Couldn't initialize communication with the Naming Service" when running the "orbadmin ns list" command, although the Naming Service process is still running. There is a firewall involved in the environment and port span of 25 is defined on the Naming service settings. |
The Operating System(OS) hosting the Control-M/Enterprise Manager(EM) is not releasing the used ports quickly enough, when a process is restarted. System administrators should investigate why the ports are not releasing by the OS when a process is restarted. |