Hi Sashi- Are you reading the message out of a Transmit queue (XMIT)? Does the message have an XQH header? If so, we have a solution for that.
Thanks, Matt Pavlovich Founding Partner Media Driver P: (512) 284-4330 E: m...@mediadriver.com Skype: mattrpav On Jun 3, 2013, at 11:20 AM, shashi.kant <shashiski...@gmail.com> wrote: > I have been trying to send message to a IBM websphere MQ queue which has to > be in IBM500 charset, MQFMT_STRING format and encoding 273 from a Camel > 2.10.4 application running on jboss.tried General ways of setting the > connectionfactory properly with following values: > *connection.setTransportType(JMSC.MQJMS_CLIENT_NONJMS_MQ); > connection.setStringProperty(WMQConstants.JMS_IBM_CHARACTER_SET, "500"); > connection.setStringProperty(WMQConstants.JMS_IBM_FORMAT, MQC.MQFMT_STRING); > connection.setIntProperty(WMQConstants.JMS_IBM_ENCODING, 273); > connection.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, > WMQConstants.WMQ_CLIENT_NONJMS_MQ);*I have tried > *IBMWebSphereMqDestinationResolver*https://jira.springsource.org/secure/attachment/12688/IBMWebSphereMqDestinationResolver.javaBut > everytime at the Websphere MQ end MQRFH2 header is there.I can't figure out > any solution to this problem..Somebody please help me out. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733713.html > Sent from the Camel Development mailing list archive at Nabble.com.
