Hi @nbommidi,
I think I understand what might be going on here. A Solace Message has two different parts of the message where a payload can be attached. The first is the Binary Attachment portion of the message, and the second is the XML Content part of the message which has hung around for legacy reasons. If you are developing new apps it is recommended to use the Binary Attachment part of the message to store your payload, which is what Spring Cloud Stream uses.
What API are your apps that are consuming the messages using? My guess is that they are using a Solace SMF API such as JCSMP and are expecting the payload to be in the “XML Content” portion of the message? Can you have them try to receive the message as a BytesMessage and use the getData method to see if your content is in there as expected?
Hope that helps!