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:

   error on read: ProtocolError: SASL layer not enabled

I'm not familiar with this. Does this mean I require a SASL client now with a username/password to authenticate? ( If so, I assume this affects the way the Java client connects as well?


On 13/02/2018 23:45, Timothy Bish wrote:
On 02/13/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!”) it is received by the Java client as a javax.jms.BytesMessage. However the contents of this BytesMessage contains a bunch of bytes in front of the actual “Hello World!” message:

   Hello World!”

I'm using the ActiveMQ's (5.13.4) and Qpid's suggested Rhea JavaScript (Node.js) library for the simple JavaScript client for testing. On the Java-side of things I'm using plain JMS 1.0.

The Rhea example I'm using is basically according to this sample:

I'm using the default AMQP configuration in order to enable the protocol in activemq.xml:

   <transportConnector name="amqp"

When I try to add "&transport.transformer=jms" or "&transport.transformer=raw" the JavaScript client is unable to connect anymore.

How do I get it so that it only contains the “Hello World!” message? Do I need to parse out the bytes contained in the BytesMessage?


Try upgrading to ActiveMQ 5.15.3 which will have improved AMQP support over that older version.

Reply via email to