MQTT only supports a bytes message, so ActiveMQ is doing what it can to deliver as an ActiveMQBytesMessage. Once you receive it, it should be a simple new String(bytes) to have the JSON in a string.
NOTE— check your character encoding handling to avoid those pain points. UTF-8, etc. > On Jan 20, 2021, at 9:47 AM, Sridhar Ayengar <[email protected]> > wrote: > > > Hi everybody. > > I’m working on an integration between AWS CloudWatch and IBM Tivoli > Netcool/OMNIbus via its Message Bus Probe. Because of various adventures, I > have settled on an architecture using a Lambda to post to a topic in Amazon > MQ, which is managed ActiveMQ Classic 5.5.14. The Lambda code uses MQTT in > Node.js to publish the message. The configuration going into OMNIbus is > straight JMS over SSL. > > The problem I’m seeing is that the message that comes into the Probe has a > data type of ActiveMQBytesMessage. OMNIbus only supports text-type messages. > Is there any way I can have message be of a text data-type? Would the > configuration be on the JMS side or the MQTT side? The message itself is > simple JSON. > > Thanks for reading. > > > > Sridhar K.N. Ayengar | Infrastructure Discovery Analyst > Infrastructure Enterprise Services > 3M Transformation, Technologies and Services > Green Island, NY 12183-1139 | United States > Mobile: +1 518 986 6301 > [email protected] <mailto:[email protected]> > > <https://twitter.com/3m> <https://www.linkedin.com/company/3m> > <https://www.facebook.com/3M> <https://instagram.com/3m/> > <https://www.youtube.com/3m> <http://www.3m.com/> > <http://www.scotchbrand.com/> <http://www.post-it.com/> > <http://www.scotch-brite.com/> <http://www.filtrete.com/> > <http://www.command.com/> <http://www.nexcare.com/> > <http://www.scotchblue.com/>
