[QPID-1119] [Java] Timeout on consumer creation with large queues

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: M2.1
• Fix Version/s: M3
• Component/s: JMS AMQP 0-x
• Assignee: Aidan Skinner
• Reporter: Marnie McCormack
• Created: 03/Jun/08 15:31
• Updated: 14/Mar/17 20:02
• Resolved: 22/Oct/08 10:59

Description

We've seen consumer timeout ("Error registering consumer: org.apache.qpid.AMQTimeoutException: Server did not respond in a timely fashion"). This was seen with volume testing, and 45,000 messages in the queue the consumer was attempting to connect to.

The issue there is that for every subscription request it needs to go over the whole queue, to work out which messages should go to which subscriber. The broker runs with number of threads == number of cores, so if you have lots of consumers they will queue up behind one another to get processed. One solution is to stagger the consumer starts on the appication side, but we can also expose the connection timeout for configuration so that applications can use this.

Thus need to create a configurable timeout for sync responses. Rob Godfrey can advise if further info required.

Issue Links

• depends upon: QPID-1103 Add ability to provide a configuration file for broker start up in java test suite