Overview

Sonic Management Console fails to establish a connection to a running Domain Manager. You are unable to connect to Domain from SMC because you receive the following error in the Sonic Management Console's Message Viewer:

java.lang.Exception: Could not establish a connection on the specified URL(s).
 at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.finished(MgmtConsole.java:290)
 at com.sonicsw.ma.gui.util.SwingWorker$1.run(SwingWorker.java:104)
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.Dialog$1.run(Unknown Source)
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)
Caused by...
com.sonicsw.mx.config.ConfigServiceException: Directory Service for Domain 'dm_sonic_test' is not responding.
 at com.sonicsw.mx.config.ConfigServerUtility.pingDirectoryService(ConfigServerUtility.java:454)
 at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:276)
 at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:248)
 at com.sonicsw.ma.gui.domain.DomainConnectionModel.connect(DomainConnectionModel.java:129)
 at com.sonicsw.ma.plugin.PluginContext.create(PluginContext.java:107)
 at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.construct(MgmtConsole.java:253)
 at com.sonicsw.ma.gui.util.SwingWorker$2.run(SwingWorker.java:110)
 at java.lang.Thread.run(Unknown Source)
Caused by...
java.lang.RuntimeException: com.sonicsw.mf.comm.InvokeTimeoutException: dm_sonic_test.DIRECTORY SERVICE:ID=DIRECTORY SERVICE - invoke()
 at com.sonicsw.mf.jmx.client.DirectoryServiceProxy.getDirectoryServiceVersion(DirectoryServiceProxy.java:382)
 at com.sonicsw.mx.config.ConfigServerUtility.pingDirectoryService(ConfigServerUtility.java:450)
 at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:276)
 at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:248)
 at com.sonicsw.ma.gui.domain.DomainConnectionModel.connect(DomainConnectionModel.java:129)
 at com.sonicsw.ma.plugin.PluginContext.create(PluginContext.java:107)
 at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.construct(MgmtConsole.java:253)
 at com.sonicsw.ma.gui.util.SwingWorker$2.run(SwingWorker.java:110)
 at java.lang.Thread.run(Unknown Source)

Solution

Domain Manager container log file shows that the Directory Service, Agent Manager and management broker all started up correctly, with no errors or exceptions. Possible explanations for this are:

1. The Directory Service is busy and is failing to respond in time. 
2. Problems with hostname mapping in DNS.
3. Running out of disk space for the domain storage. 
4. Although the domain manager appears from its log file to be running normally, its container can't create a management connection because it was started with an incorrect "ConnectionURLs" value.  The only indicator of this problem in the container log file is the absence of the following message that normally appears when the container has started successfully:
      (info) Management connection (re)established

Fixes for each of the potential causes listed above are:

1. Increase the Connect Timeout when creating the connection in SMC.
2. Ask network administrators to verify that hostname mapping is functioning correctly. 
3. Check there is enough disk space on the system.
4. Perform this sequence of actions:
   1. Shut down the running domain manager container. 
   2. Connect offline to the DS and correct the Connection URL(s) value in the container's properties, and regenerate the container boot file.  
   3. Restart the domain manager and verify that the container logs the message “Management connection (re)established”.
   4. Try again to connect with SMC.