We are reading from a websphere mq which reads about 36-40msg/s which is very slow. We are using this in a liberty profile environment. The old version, which is on Java Caps on websphere is 3x faster. Not ok.
The code is basically this (one of out components): from(wmq:queue:inqueue).to(direct:handler); from(direct:handler).to(wmq:queue:outqueue); *Concurrent consumers would make it faster, BUT, we need the messages in the correct order. Is using concurrentConsumers + resequencer the only alternative? Are there any more alternatives? Are there any risks with using resequencer?* And the jms component looks like: -- View this message in context: http://camel.465427.n5.nabble.com/Camel-tuning-Reading-Websphere-MQ-is-slow-35-40msg-s-tp5774679.html Sent from the Camel - Users mailing list archive at Nabble.com.
