Hi,
I have a map which is writing to a JMS queue. When testing the map from my desktop, the map was writing successfully to the JMS queue and the application was being able to read the message properties and the message body separately.
However when I deployed it to our staging box, i found that the application reading from the staging queue was combining the message properties and the message body and was thus giving an error because the entire message (XML)was not valid.
Is there some setting in Weblogic queues or in the JMS adapter which could cause this?
Thanks
I have a map which is writing to a JMS queue. When testing the map from my desktop, the map was writing successfully to the JMS queue and the application was being able to read the message properties and the message body separately.
However when I deployed it to our staging box, i found that the application reading from the staging queue was combining the message properties and the message body and was thus giving an error because the entire message (XML)was not valid.
Is there some setting in Weblogic queues or in the JMS adapter which could cause this?
Thanks