You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2008/06/03 17:32:44 UTC
[jira] Created: (QPID-1119) [Java] Timeout on consumer creation
with large queues
[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 Broker
Affects Versions: M2.1
Reporter: Marnie McCormack
Fix For: M3
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.
[jira] Resolved: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1119.
---------------------------------
Resolution: Fixed
Fine, just remember to re-enable this for the Java broker when QPID-1103 is fixed
> [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: Aidan Skinner
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1119:
---------------------------------
Status: Ready To Review (was: In Progress)
> [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.
[jira] Commented: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-1119:
--------------------------------
Status: Open (was: Ready To Review)
Patch looks OK, the test has been failing in cruise control though.
> [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: Aidan Skinner
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1119:
---------------------------------
Status: Ready To Review (was: In Progress)
> [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.
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1119:
------------------------------------
Assignee: Martin Ritchie
> [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: M3
>
>
> 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.
[jira] Commented: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620648#action_12620648 ]
Aidan Skinner commented on QPID-1119:
-------------------------------------
Needs test, shouldn't be a problem post refactor
> [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: M3
>
>
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1119:
---------------------------------
Status: Ready To Review (was: In Progress)
> [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.
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-1119:
-----------------------------------
Assignee: Martin Ritchie (was: Aidan Skinner)
> [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.
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner reassigned QPID-1119:
-----------------------------------
Assignee: Martin Ritchie (was: Aidan Skinner)
> [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.
[jira] Commented: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757858#action_12757858 ]
Martin Ritchie commented on QPID-1119:
--------------------------------------
FAQ Entry
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+FAQ#QpidJavaFAQ-Clientkeepsthrowing%27Serverdidnotrespondinatimelyfashion%27.
> [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: Aidan Skinner
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1119:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hi Aidan, The test has been re-enabled on for InVM tests the Java Profile testing will need QPID-1103 to be completed first.
> [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: Aidan Skinner
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner updated QPID-1119:
--------------------------------
Status: Open (was: Ready To Review)
Now there is a test, but it's been disabled.
> [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: Aidan Skinner
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1119:
---------------------------------
Component/s: (was: Java Broker)
Java Client
> [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: M3
>
>
> 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.
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1119:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Aidan can you review this change please.
> [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: Aidan Skinner
> 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.
[jira] Commented: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639863#action_12639863 ]
Martin Ritchie commented on QPID-1119:
--------------------------------------
The test had been disabled but QPID-1262 does not block this issue.
The reason that the SWTDT was failing was that we have no way to start an external broker with a specified broker.
JIRA to follow.
> [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.
[jira] Assigned: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1119:
------------------------------------
Assignee: Aidan Skinner (was: Martin Ritchie)
Hey can you review this form me?
> [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: Aidan Skinner
> 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.
[jira] Updated: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1119:
---------------------------------
Fix Version/s: (was: M4)
M3
> [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: Aidan Skinner
> Fix For: M3
>
>
> 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.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1119) [Java] Timeout on consumer creation
with large queues
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628301#action_12628301 ]
Martin Ritchie commented on QPID-1119:
--------------------------------------
SyncWaitTimeoutDelayTest has been disabled as per QPID-1262.
> [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.