I made the test with WebSphere MQ 7.0.1.3 and also didn't see any problems.
It tooks 101ms to receive the response (with persistent messaging).
{code}
2011-01-26 00:37:15,344 [main ] DEBUG
Configuration$CamelJmsTemplate - Sending JMS message to: queue:///hello with
message:
JMSMessage class: jms_text
JMSType: null
JMSDeliveryMode: 2
JMSExpiration: 0
JMSPriority: 4
JMSMessageID: null
JMSTimestamp: 0
JMSCorrelationID: 50a73c9e-0894-4454-9bf0-e8d4d5d6f3a2
JMSDestination: null
JMSReplyTo:
queue:///AMQ.4D3F5794025F0020?OBJECT_IDENTITY=2001229122&persistence=1
JMSRedelivered: false
foo: 123
Hello World
2011-01-26 00:37:15,424 [main ] DEBUG JmsProducer
- Message sent, now waiting for reply at:
queue:///AMQ.4D3F5794025F0020?OBJECT_IDENTITY=2001229122&persistence=1
2011-01-26 00:37:15,445 [main ] DEBUG JmsProducer
- Reply received. Setting reply as OUT message: Bye World
{code}
I used the following configuration in
org.apache.camel.component.jms.JmsSimpleRequestReplyTest:
{code}
protected CamelContext createCamelContext() throws Exception {
CamelContext camelContext = super.createCamelContext();
MQQueueConnectionFactory connectionFactory = new
MQQueueConnectionFactory();
JmsConfiguration jc = new JmsConfiguration(connectionFactory);
connectionFactory.setHostName("172.16.2.128");
connectionFactory.setPort(1414);
connectionFactory.setQueueManager("QM_christia_7ukqif");
connectionFactory.setTransportType(1);
camelContext.addComponent("webspheremq",
jmsComponentClientAcknowledge(connectionFactory));
return camelContext;
}
{code}
and added the following jars from ${WebSphere_MQ_HOME}/java/lib:
- com.ibm.mq.jar
- com.ibm.mq.jmqi.jar
- com.ibm.mqjms.jar
- dhbcore.jar
Christian
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-InOut-Performance-Issues-with-Correlation-Mechanism-tp489714p3357185.html
Sent from the Camel Development mailing list archive at Nabble.com.
