# NOt able to see message content on Try-Me on Solace on docker

**URL:** <https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262>\
**Category:** Solace Event Portal\
**Tags:** jms, docker, broker\
**Created:** [May 3, 2020, 3:06pm UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262 "2020-05-03T15:06:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![harry](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/harry/32/1464_2.png) [@harry](https://community.solace.com/u/harry)\
**Post date:** [May 3, 2020, 3:06pm UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/1 "2020-05-03T15:06:06Z")

</div>

I have solace running on docker and have used JMS API to send message to a queue (the topic named "dt’ is subscribed to queue named "que1’). The event is received through the code as  
2020-05-03 20:34:30:300 [Topic dt]  
Delivery Mode:  
Persistent  
Sender Timestamp:  
2020-05-03 20:34:12:510  
Priority:  
4

But the conntent of message is not visible. When i send the message through java script running in Try-Me publisher the message is shown .ANy help?

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [May 4, 2020, 8:42am UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/2 "2020-05-04T08:42:02Z")

</div>

Hey @harry. Are you sending a text message? I would check your JMS connection factory. It’s most likely configured to use the “XML Portion” of the payload:

```auto
6650bdcff498> show jndi connection-factory * detail

Connection Factory : /jms/cf/default
Message VPN : default
  messaging-properties : 6
    default-delivery-mode : persistent
    text-msg-xml-payload : true <-------

```

This is due to some old-school legacy configuration. (there are actually 2 separate payload sections in Solace messages, FYI). Anyhow, the “Try Me!” mini app only shows data from the binary portion of the payload. Solace is aware of this and is planning to fix soon.

So, either change your connection factory to set “text-msg-xml-payload” to false **_OR_** try sending a Bytes/binary message instead with your UTF-8 String as payload. I’d recommend the 2nd option, as then you can easily interoperate with non-Solace APIs and protocols, like MQTT.

---

<div class="post-metadata">

**Author:** ![harry](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/harry/32/1464_2.png) [@harry](https://community.solace.com/u/harry)\
**Post date:** [May 4, 2020, 11:46am UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/3 "2020-05-04T11:46:00Z")

</div>

Hi @Aaron , yes i was sending a text message.  
I changed that too  
BytesMessage message  
message=session.createBytesMessage();//(res);  
message.writeUTF(res); ``  
messageProducer.send(topic,message);

and it worked like a charm. Thanks for the help. But if i send a text message to an actual solace queue in production (basically publishing to topics binded to a queue) , then the broker will publish the data to consumers through REST API, ) that should not be an issue right?

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [May 4, 2020, 12:35pm UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/4 "2020-05-04T12:35:03Z")

</div>

Ah, interesting. You are configuring a queue and an RDP to “webhook” the messages out to a REST endpoint? Either way, no I don’t think it should be a problem. In fact, I think it should be less of a problem than having it configured the previous way.

Always best to test. I don’t know 100.000% off the top of my head. 😉

But hey, you could also implement my 1st suggestion where you just change the JMS connection factory to say “false” for `text-msg-xml-payload` and both should work the same… the Try Me! mini app should see it… and the outbound RDP REST API should convert it just the same.

---

<div class="post-metadata">

**Author:** ![marc](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/marc/32/2191_2.png) [@marc](https://community.solace.com/u/marc)\
**Post date:** [May 4, 2020, 1:47pm UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/5 "2020-05-04T13:47:35Z")

</div>

@harry, on top of the tips that @Aaron provided you I would like to say that we have also opened a bug against the try-me tab to to show the payload when `text-msg-xml-payload` is set to true.

---

<div class="post-metadata">

**Author:** ![harry](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/harry/32/1464_2.png) [@harry](https://community.solace.com/u/harry)\
**Post date:** [May 5, 2020, 5:59am UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/6 "2020-05-05T05:59:55Z")

</div>

Sure @Aaron , and thanks @marc , i am just getting started with solace, lots of things to learn and understand and hopefully you are gonna hear more from me, cheers.

---

<div class="post-metadata">

**Author:** ![marc](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/marc/32/2191_2.png) [@marc](https://community.solace.com/u/marc)\
**Post date:** [July 15, 2020, 3:53pm UTC](https://community.solace.com/t/not-able-to-see-message-content-on-try-me-on-solace-on-docker/262/7 "2020-07-15T15:53:03Z")

</div>

Hey @harry!  
Hope all is going well with your Solace learnings! I just wanted to let you, and anyone else that finds this thread, know that the latest broker release, `v9.6.0.27`includes support in the “Try-Me!” for messages that have `text-msg-xml-payload` set to `true`.