[
https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639866#action_12639866
]
Martin Ritchie commented on QPID-1119:
--------------------------------------
This issue is not blocked by QPID-1262 as mentioned above.
> [Java] Timeout on consumer creation with large queues
> -----------------------------------------------------
>
> Key: QPID-1119
> URL: https://issues.apache.org/jira/browse/QPID-1119
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: M2.1
> Reporter: Marnie McCormack
> Assignee: Martin Ritchie
> Fix For: M4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
