On 02/13/2018 07:29 PM, Jeroen van Ooststroom wrote:
Now you need to switch to the JMS transformer to achieve cross protocol
I added the wireFormat.allowNonSaslConnections=true to the AMQP
transport connector configuration which resolves the issue of the
the same kind of BytesMessage at the Java-side as mentioned in the
original post with the added 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:
Yes, you need to either connect via SASL or configure the
transportConnector to accept non-SASL connections if you have not
secured your broker (you really should secure your broker).
Thank you for your response.
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:
ActiveMQ using AMQP and our Java client that connects to the same
ActiveMQ using OpenWire (JMS). When I send a message from the
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:
Try upgrading to ActiveMQ 5.15.3 which will have improved AMQP
support over that older version.
I'm using the ActiveMQ's (5.13.4) and Qpid's suggested Rhea
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:
When I try to add "&transport.transformer=jms" or
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