bytes before the "Hello World!" string.
On 14/02/2018 00:46, Timothy Bish wrote:
On 02/13/2018 06:22 PM, Jeroen van Ooststroom wrote:
Thank you for your response.
When I upgrade to ActiveMQ 5.15.3 my simple JavaScript client isn't
able to connect to the AMQP connector anymore:
/2018 05:29 PM, Jeroen van Ooststroom wrote:
I have a simple test JavaScript (Node.js) client that connects to
ActiveMQ using AMQP and our Java client that connects to the same
ActiveMQ using OpenWire (JMS). When I send a message from the
JavaScript client (just a simple “Hello World
I have a simple test JavaScript (Node.js) client that connects to
ActiveMQ using AMQP and our Java client that connects to the same
ActiveMQ using OpenWire (JMS). When I send a message from the JavaScript
client (just a simple “Hello World!”) it is received by the Java client
as a
Hello,
Coming back to the discussion on the apache-activemq IRC channel of
possible Topics and Queues when using ActiveMQ’s MQTT service.
First a bit of history then. We’ve have been using multiple Java-based
services for quite a bit of years now utilizing ActiveMQ’s JMS Topic and
the
tched version until someone else implements
a permanent fix for the mainline ActiveMQ codebase.
4. Use some form of runtime bytecode manipulation to modify the value of
the mcNetworkInterface field without modifying the ActiveMQ code. Maybe it
would be possible to do this via AOP, or a mocking frame
Hi all,
I tried with the latest ActiveMQ 5.15.1 as well, but I unfortunately get the
same result: it still won't do the automatic clustering, while locally using
VMs this still works.
Thanks,
Jeroen...
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi all,
I’m stuck with getting an ActiveMQ cluster going within a Docker
environment using Weave. The environment runs on an Amazon AWS ECS
Cluster of 2 EC2 Instances running in the same Region, but in different
Availability Zones. The clustering of ActiveMQ must rely on multicast
due to the
