No idea. Next steps are probably to turn on tracing on the Camel Context so that it logs a record of every message sent. Then you can use that to correlate and see if Camel thinks the JMS provider accepted the message, then start looking at possibly the messages being lost by the JMS implementation. Additionally, think about registering an ExceptionListener to see if the JMS is reporting any useful information about lost messages.
-----Original Message----- From: RadoslavStoyanov [mailto:radoslav.stoya...@softwareag.com] Sent: Thursday, December 08, 2011 8:38 AM To: users@camel.apache.org Subject: RE: Performance issue with Camel JMS publish/subscribe Hi Sven, Adding the cached factory wrapper increased the performance with 800%! Now I have another issue, when I do threaded send - 10 threads publish to the same endpoint and one consumer - it happens that some of the messages are lost (didn't reach the consumer) - not a big number, but there are lost messages. The broker is local, so no network issues are possible. Do you think this could be because of endpoint setup? Regards, Rado -- View this message in context: http://camel.465427.n5.nabble.com/Performance-issue-with-Camel-JMS-publish-subscribe-tp5049909p5059357.html Sent from the Camel - Users mailing list archive at Nabble.com.
