Hi @akg17 ,
Okay, so I think what is happening is as follows ( @amackenzie please correct me if I’m wrong 
):
You have a JMS App (App 1) sending a message, which is received and processed by a Spring Cloud Stream app (App 2) which then publishes a new message. That new message is being received by another JMS app (App 3). Correct?
The Spring Cloud Stream app is publishing a BytesMessage which the Broker is then delivering to the JMS app (App 3) as a SolBytesMessage. It is not a JMS TextMessage, which is why it can’t be read as such. . Because of that I think the code you have looks correct, the payload of that SolBytesMessage would be read and then converted to a String for your app to process. Will that not work for you?
If for some reason you can’t change the app that is expecting a JMS TextMessage then you will need to explicitly publish a JMS Text Message using our JMS API. To do that you could either write a pure JMS app instead of using Cloud Stream or you could even receive using Cloud Stream + Send via JMS. Here is an example of an app that actually does that.
Hope that helps!