A workaround I'm using is to add a processor on the end of my pipeline to
remove the JMS_IBM_MsgType property. When I do this Websphere is fine (uses
a datagram type for the reply though - I guess I could set it explicitly to
2).
eg:
.process(new Processor() {
@Override
public void process(Exchange exchange) throws
Exception {
exchange.getIn().removeHeader("JMS_IBM_MsgType");
}
})
--
View this message in context:
http://camel.465427.n5.nabble.com/SJMS-component-and-IBM-Websphere-MQ-quirks-tp5740588p5740596.html
Sent from the Camel - Users mailing list archive at Nabble.com.
