Error is thrown in the console when the JMS Physical destination Tab is clicked for a standalone instance on a remote SSH node. Steps to reproduce:
--Create a SSH node on a remote machine.
--Create a std instance on this remote node and start the instance.
--Select the running instance in the left tree node.
--In the right window, click on the JMS Physical destination Tab.
--The below Error is seen in the Console:
An error has occurred
Unable to list JMS Destinations. Please ensure that the Message Queue Brokers are running.
Attached screen shot.
When we have a cluster with a local instance and a remote instance ( on a remote SSH node), The first time we click on the JMS Physical destinations tab for the running cluster, An Error is thrown in the console as well.
--create a cluster with 2 instances ( a local instance and a remote instance on a remote SSH node)
--start the cluster.
--select the cluster in the left tree,and in the right window click on the JMS physical destination tab.
The Console launches the popup "A long running process has been detected"..After a while we see the error in the console.