Hi Rajib, There are many reasons why an operation can time out.
Can you provide more of your client log, especially the stack trace of the exception? Do you see any errors or warning in your broker or client log before the problem occurs? What makes you think this is a "slow consumer issue", and how would you define it? I'm particularly interested in this because the reported error says "Exception when _sending_ message". Can you tell us anything else about the test that might help to diagnose the problem? Phil On 5 July 2013 07:50, <[email protected]> wrote: > Hi All, > > I am using qpid 0.22, JMS client and C++ broker. > > > Doing some stress test with queue producers and consumers, Java producer > using JMS qpid library fails to publish a message, logging: > "javax.jms.JMSException: Exception when sending message: timed out waiting > for completion" exception. > > I am running both producer and consumer on the same Linux RHEL 5 host. > > It sounds like a slow consumer issue, which is unexpected on the same host. > > Can you someone please let me know why is this happening ? > > Thanks > > Rajib > > > > > > > > > > > > > _______________________________________________ > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary > from Barclays Sales and/or Trading, who are active market participants; and > in respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com. > > _______________________________________________ >
