Re: MQTT to JMS conversion results in null message body.

[coolboy]

I see a similar behavior with HTTP too. 

I do a HTTP GET with a timeout of 30s on a topic string say, a.b.c. And,
from a mosquitto_pub client, I do a publish with/without retain flag to
a/b/c. I get a HTTP STATUS 200 OK, but, the message body is null.

What is going on  ?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/MQTT-to-JMS-conversion-results-in-null-message-body-tp4681107p4681147.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

MQTT to JMS conversion results in null message body.

[coolboy]

Is there something special to be done to ensure message body from a MQTT
client appears in the JMS message body ?

I am using the mosquitto publish client to publish a simple message to
amq/mqtt/sample topic string on ActiveMQ. As expected, the JMS conversion
happens correctly. I can see amq.mqtt.sample topic string under Topics in
the web console. To see if the message appears successfully at the JMS end,
I started jconsole. (Yes, I tried SoapUI and couple of others; they failed
to work for one or other reason). jconsole does not show any message body
for the said topic string. However, when I send a message to amq.mqtt.sample
topic string from jconsole or web console, I can see them correctly in the
mosquitto subscribe client.

This problem exists even when I publish from mosquitto publish client with
retain flag turned on. For example,

Without retain flag
mosquitto_pub -p port_number -i clientId -t amq/mqtt/sample -l 

mosquitto_pub -p port_number -i clientId -t amq/mqtt/sample -r -l 




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/MQTT-to-JMS-conversion-results-in-null-message-body-tp4681107.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.