I have an update on this issue. I tried using an annotated POJO approach
rather than just the from.("jetty:...").process(...).to("activemq:") method.
For whatever reason, I'm now seeing closer to 600 msg/sec (up from
~150/sec). Here is the code...
@Produce(uri="activemq:GatewayMsgQueue")
ProducerTemplate producer;
@Consume(uri="jetty:http://0.0.0.0:9000/inboundMessage";)
public void onMessage(String msg) {
//logger.debug("onMessage->" + msg);
producer.sendBody(msg);
}
Anyone know why this approach increased throughput so much? I no longer
have to explicitly convert the inbound data using the process() step to get
it to AMQ...this approach must be doing that on its own. If anyone knows
why this approach seems to be much more efficient, let me know.
thanks
-----
Ben - Senior Consultant
--
View this message in context:
http://www.nabble.com/Camel-throughput-issues...HTTP-to-AMQ-tp24648117p24658972.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
