Hi,
I am beginner to SONIC ESB. I started the Domain Manager using Start Domain Manager option. The SONIC version is
Release 7.6.1 Build Number 198 Protocol P30
I opened the Sonic Management Console and try to create a connection for the default domain Connection1, Domain1, tcp://localhost:2506. I am getting the following exception in the SONIC Management Console
Can anyone help me what am I missing?
Thanks,
Guru
java.lang.Exception: Could not establish a connection on the specified URL(s).
Directory Service for Domain 'Domain1' is not responding.
at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.finished(MgmtConsole.java:376)
at com.sonicsw.ma.gui.util.SwingWorker$1.run(SwingWorker.java:104)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:153)
at java.awt.Dialog$1.run(Dialog.java:525)
at java.awt.Dialog$2.run(Dialog.java:553)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:551)
at java.awt.Component.show(Component.java:1300)
at java.awt.Component.setVisible(Component.java:1253)
at com.sonicsw.ma.gui.util.JProgressDialog.setVisible(JProgressDialog.java:105)
at com.sonicsw.ma.gui.MgmtConsole.connectToDomain(MgmtConsole.java:287)
at com.sonicsw.ma.gui.MgmtConsole.connectToDefaultDomain(MgmtConsole.java:248)
at com.sonicsw.ma.gui.ToolBar$FileConnectAction.actionPerformed(ToolBar.java:428)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:5501)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
at java.awt.Component.processEvent(Component.java:5266)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3968)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1778)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Caused by: com.sonicsw.mx.config.ConfigServiceException: Directory Service for Domain 'Domain1' is not responding.
at com.sonicsw.mx.config.ConfigServerUtility.pingDirectoryService(ConfigServerUtility.java:478)
at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:278)
at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:248)
at com.sonicsw.ma.gui.domain.DomainConnectionModel.connect(DomainConnectionModel.java:141)
at com.sonicsw.ma.plugin.PluginContext.create(PluginContext.java:114)
at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.construct(MgmtConsole.java:337)
at com.sonicsw.ma.gui.util.SwingWorker$2.run(SwingWorker.java:110)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.sonicsw.mf.comm.InvokeTimeoutException: Domain1.DIRECTORY SERVICE:ID=DIRECTORY SERVICE - invoke()
at com.sonicsw.mf.comm.jms.ConnectorClient.invoke(ConnectorClient.java:836)
at com.sonicsw.mf.comm.jms.ConnectorClient.invoke(ConnectorClient.java:631)
at com.sonicsw.mf.jmx.client.JMSConnectorClient.invoke(JMSConnectorClient.java:850)
at com.sonicsw.mf.jmx.client.JMSConnectorClient.invoke(JMSConnectorClient.java:807)
at com.sonicsw.mf.jmx.client.DirectoryServiceProxy.getDirectoryServiceVersion(DirectoryServiceProxy.java:413)
at com.sonicsw.mx.config.ConfigServerUtility.pingDirectoryService(ConfigServerUtility.java:474)
at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:278)
at com.sonicsw.mx.config.ConfigServerUtility.connect(ConfigServerUtility.java:248)
at com.sonicsw.ma.gui.domain.DomainConnectionModel.connect(DomainConnectionModel.java:141)
at com.sonicsw.ma.plugin.PluginContext.create(PluginContext.java:114)
at com.sonicsw.ma.gui.MgmtConsole$ConnectWorker.construct(MgmtConsole.java:337)
at com.sonicsw.ma.gui.util.SwingWorker$2.run(SwingWorker.java:110)
at java.lang.Thread.run(Thread.java:595)
Guru,
gurusanka schrieb:
Hi,
I am beginner to SONIC ESB. I started the Domain Manager using Start Domain Manager option. The SONIC version is
Release 7.6.1 Build Number 198 Protocol P30
I opened the Sonic Management Console and try to create a connection for the default domain Connection1, Domain1, tcp://localhost:2506. I am getting the following exception in the SONIC Management Console
Can anyone help me what am I missing?
Thanks,
Guru
how you starting the domain manager? From the Workbench or the Start Menu?
If from the start menu do you have a console window open? Can you paste the output of it?
You probably just a have a mismatch between the information given (Domain1, and localhost:2506) and what is actually used.
Thomas
Hi Thomas,
Thanks for your update.
1. I started the Domain Manager from the Start up Menu
2. I get the following log messages (copied from Domain1.DomainManger.log file)
[10/01/28 09:23:34] (info) "Domain1.DomainManager" starting...
[10/01/28 09:23:45] (warning) Management connect failure: java.net.ConnectException: Connection refused: connect: tcp://localhost:2506
[10/01/28 09:23:45] (info) ...connect failed, retrying...
[10/01/28 09:23:46] (info) Loaded ID=AGENT
[10/01/28 09:23:46] (info) Loaded ID=DIRECTORY SERVICE
[10/01/28 09:23:51] (info) Loaded ID=AGENT MANAGER
[10/01/28 09:23:52] (info) Loaded ID=AutoLaunchDaemon
[10/01/28 09:23:54] (info) Loaded ID=MgmtBroker
[10/01/28 09:23:54] ID=MgmtBroker (config)
SonicMQ Professional Developer Edition [Serial Number 999999999]
Release 7.6.1 Build Number 198 Protocol P30
Copyright (c) 1999-2008 Progress Software Corporation.
All Rights Reserved.
Broker "MgmtBroker". Routing Node "MgmtBroker".
There is no limit on the number of concurrent connections.
Security is enabled. Interbroker is disabled.
Dynamic Routing is enabled. HTTP Direct is enabled.
[10/01/28 09:23:55] ID=MgmtBroker (info) Registering node "sonic.http" of "$RNN.sonic$http.$HTTP.undefinedroutingurl.9999" for routing node reverse lookup
[10/01/28 09:23:56] ID=MgmtBroker (info) Starting recovery...
[10/01/28 09:23:56] ID=MgmtBroker (info) Recovery complete.
[10/01/28 09:23:57] ID=MgmtBroker (info) Restoring queues ...
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SonicMQ.deadMessage" - Local Non-clustered Shared 1536 16384
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SonicMQ.routingQueue" - Local Non-clustered Shared 1536 1024
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q9" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SampleQ4" - Local Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q8" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SampleQ3" - Local Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q7" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SampleQ2" - Local Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q6" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "SampleQ1" - Local Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q5" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q4" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q3" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q2" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) Starting queue "Sample.Q1" - Global Non-clustered Shared 1536 1000
[10/01/28 09:23:57] ID=MgmtBroker (info) dev.HTTPDirect: accepting connections on http://WRKSWIDEDI45608:2580
[10/01/28 09:23:57] ID=MgmtBroker (info) TCP_ACCEPTOR: accepting connections on tcp://WRKSWIDEDI45608:2506
[10/01/28 09:23:57] ID=MgmtBroker (info) SonicMQ Broker started
[10/01/28 09:23:57] (info) ...startup complete
[10/01/28 09:23:58] (info) Management connection (re)established (Socket[addr=localhost/127.0.0.1,port=2506,localport=1705])
3. Started the Sonic Management Console.
4. From SMC, tried to connect to the Domain Manager with the following parameters.
Connection Name: Connection1
Domain Name: Domain1
Connection URL : tcp://localhost:2506
5. A windows pop ups and said trying to connect
6. After few seconds, it has thrown an error message
7. From the Message Viewer, I am getting the exception which I have pasted above
Please help me out in resolving this issue.
And also I tried to open the Work Bench (after shutting down the Domain Manager which I started from
the Start up Menu, because I assume the work bench will try to start its own Domain Manager), then tried to connect to the
Domain Manager, no luck.. getting the same error messsage. If I try to connect to the Domain Manager (leaving the Domain Manager which
I started from the Start up Menu, open) from the workbench, I get an error message that "A Domain Manager is already running".
Thanks,
Guru
Try using the exact connection, and not using "localhost". I think for you (looking at the domain manager log) that it is
tcp://WRKSWIDEDI45608:2506
Use user and password "Administrator"
Finally, did you choose any 'non-default' options in the install. That might help locate the issue.
And also I tried to open the Work Bench (after shutting down the Domain Manager which I started from
the Start up Menu, because I assume the work bench will try to start its own Domain Manager), then tried to connect to the
Domain Manager, no luck
Two things here...
Hi,
Thanks for your update.
In fact I had tried to use 'localhost' and machine name both for connecting the domain manager, but i get the same error message for both.
When connecting, I used the 'Administrator' and 'Administrator' as user credentials. The installation is done by a different Team
in my office. But when I look at the container.xml, i could understand that 'Administrator' credentials are used for Domain Manager
I understood the concept of Domain Manager and Work bench, I have been trying out all the options, but not able to figure out the issue
Thanks,
Guru
I am unsure what the problem is, but one thing is this....
1. Verify that the container.xml you are pointing to is really the one that the domain manager is using. It probably is.
2. The fact that the Domain Manager successfully starts implies that the Management Broker is reachable over URL=tcp://localhost:2506, User/Pwd=Administrator. For the broker to start it, it needs to have its own container connect to it. This line says that this worked:
10/01/28 09:23:58] (info) Management connection (re)established (Socket[addr=localhost/127.0.0.1,port=2506,localport=1705])
3. The install done by your IT department did use "localhost". Usually the machine name is used. While this probably did not cause an issue, it is possible it did, but for now don't redo anything.
Given the above, it is probably just a simple configuration error. I would suggest the following:
1. Find someone who has Sonic running on another machine.
2. Try to connect from your SMC to their machine. Use the same user/pwd (but definitely don't use localhost). Can you connect to somewhere else?
3. Can that installation's SMC connect to your machine?
Finally, you might try just running any of the samples, or the JMS Test Client. Can anything (not just SMC) connect? Can the JMS Test client connect and send messages?