Reputation: 959
I have a new install of ActiveMQ Artemis on a local virtual machine using Ubuntu 18.04. I'm trying to connect to it with a JMS client called QueueExplorer.
Cannot read queues from machine 192.168.1.13/ (ActiveMQ).
StackTrace: Cogin.ActiveMQ.AMQException: Could not connect to ActiveMQ: Unable to connect to the remote server
at Cogin.ActiveMQ.Internal.JolokiaConnection.SendJsonRequest(String uriString, JToken requestJson)
at Cogin.ActiveMQ.Internal.JolokiaConnection.RequestBrokerName()
at Cogin.ActiveMQ.Internal.JolokiaRequest.GetMBeanObject(AMQMachineItem machine)
at Cogin.ActiveMQ.Internal.JolokiaConnection.Execute(JolokiaRequest request)
at Cogin.ActiveMQ.Internal.AMQBrokerProxy.GetBrokerInfo(IWorker worker)
at Cogin.ActiveMQ.Services.AMQBrokerService.GetQueuesTree(IWorker worker, Boolean showNonWritableQueues)
at a8.a.e(IWorker A_0)
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at ab.a.e()
Version: QueueExplorer Standard 4.3.15.26129 .Net Framework Version: 4.8.0 OS: Windows 10
I can ping the system successfully. The firewall is not enabled, and I can reach the web console. I followed this guide for setting it up, but I think I'm missing something. QueueExplorer needs Jolokia and OpenWire. The web console uses Jolokia, but the error in QueueExplorer complains about it.
When connecting to ActiveMQ with QueueExplorer, I didn't need to make any configuration changes. Are there additional steps in Artemis to allow a client to connect?
Upvotes: 1
Views: 570
Reputation: 34973
It's impossible to say with 100% certainty what the problem is since QueueExplorer is closed source software as far as I can tell. However, I can say with certainty that ActiveMQ Artemis does support OpenWire and it ships with Jolokia to expose its management beans (i.e. MBeans) via HTTP.
I believe the issue is that QueueExplorer expects to find in ActiveMQ Artemis the same MBeans as ActiveMQ 5.x and that simply isn't the case. While ActiveMQ Artemis supports many of the same features and functionality as ActiveMQ 5.x it is a fundamentally different architecture under the covers which is designed to provide a much higher level of performance and a protocol/API agnostic addressing model.
I believe the only solution here would be for the author(s) of QueueExplorer to update it to work with the ActiveMQ Artemis MBeans.
Upvotes: 1