You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2009/12/11 21:48:18 UTC

[jira] Created: (QPID-2266) error sending update: Enqueue capacity threshold exceeded

 error sending update: Enqueue capacity threshold exceeded
----------------------------------------------------------

                 Key: QPID-2266
                 URL: https://issues.apache.org/jira/browse/QPID-2266
             Project: Qpid
          Issue Type: Bug
            Reporter: Alan Conway


>From https://bugzilla.redhat.com/show_bug.cgi?id=509796
Description of problem:

Adding a new node to a cluster failed with a journal capacity exception.
However the new node was using the default journal size options as was the
existing cluster node so its not clear why this error should occur.

Version-Release number of selected component (if applicable):

qpidd-0.5.752581-22.el5
rhm-0.5.3206-5.el5

How reproducible:

Fairly easily

Steps to Reproduce:
1. start one cluster node
2. run  while perftest --durable true --count 50000 --size 8 --summary; do
true; done
3. while this is running add a new node to the cluster, then stop it, then
re-add it and repeat this for several times until eventually you see an error

Actual results:

2009-jul-06 05:07:10 notice Journal "perftest0": Created
2009-jul-06 05:07:11 warning Journal "perftest0": Enqueue capacity threshold
exceeded on queue "perftest0".
2009-jul-06 05:07:11 error Unexpected exception: Enqueue capacity threshold
exceeded on queue "perftest0". (JournalImpl.cpp:576)
2009-jul-06 05:07:11 error Connection 10.16.44.221:46092 closed by error:
Enqueue capacity threshold exceeded on queue "perftest0".
(JournalImpl.cpp:576)(501)
2009-jul-06 05:07:11 error Channel exception: not-attached: Channel 1 is not
attached (qpid/amqp_0_10/SessionHandler.cpp:40)
2009-jul-06 05:07:11 critical 10.16.44.221:19499(UPDATEE) catch-up connection
closed prematurely 10.16.44.221:19499-1(local,catchup)
2009-jul-06 05:07:11 notice 10.16.44.221:19499(LEFT) leaving cluster
grs-mrg14-test-cluster
2009-jul-06 05:07:11 notice Shut down


Expected results:

Should always be able to add the new node since the queue on the original node
in the cluster has the same capacity.



-- 
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-2266) error sending update: Enqueue capacity threshold exceeded

Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789519#action_12789519 ] 

Alan Conway commented on QPID-2266:
-----------------------------------

The problem  is that the message header are different (and  larger) on a joining node than  on nodes that were part of the cluster when it was published. On the updatee the messages-transfer.destination has the "qpid.cluster-update" destination instead of the original destination. 

>  error sending update: Enqueue capacity threshold exceeded
> ----------------------------------------------------------
>
>                 Key: QPID-2266
>                 URL: https://issues.apache.org/jira/browse/QPID-2266
>             Project: Qpid
>          Issue Type: Bug
>            Reporter: Alan Conway
>
> From https://bugzilla.redhat.com/show_bug.cgi?id=509796
> Description of problem:
> Adding a new node to a cluster failed with a journal capacity exception.
> However the new node was using the default journal size options as was the
> existing cluster node so its not clear why this error should occur.
> Version-Release number of selected component (if applicable):
> qpidd-0.5.752581-22.el5
> rhm-0.5.3206-5.el5
> How reproducible:
> Fairly easily
> Steps to Reproduce:
> 1. start one cluster node
> 2. run  while perftest --durable true --count 50000 --size 8 --summary; do
> true; done
> 3. while this is running add a new node to the cluster, then stop it, then
> re-add it and repeat this for several times until eventually you see an error
> Actual results:
> 2009-jul-06 05:07:10 notice Journal "perftest0": Created
> 2009-jul-06 05:07:11 warning Journal "perftest0": Enqueue capacity threshold
> exceeded on queue "perftest0".
> 2009-jul-06 05:07:11 error Unexpected exception: Enqueue capacity threshold
> exceeded on queue "perftest0". (JournalImpl.cpp:576)
> 2009-jul-06 05:07:11 error Connection 10.16.44.221:46092 closed by error:
> Enqueue capacity threshold exceeded on queue "perftest0".
> (JournalImpl.cpp:576)(501)
> 2009-jul-06 05:07:11 error Channel exception: not-attached: Channel 1 is not
> attached (qpid/amqp_0_10/SessionHandler.cpp:40)
> 2009-jul-06 05:07:11 critical 10.16.44.221:19499(UPDATEE) catch-up connection
> closed prematurely 10.16.44.221:19499-1(local,catchup)
> 2009-jul-06 05:07:11 notice 10.16.44.221:19499(LEFT) leaving cluster
> grs-mrg14-test-cluster
> 2009-jul-06 05:07:11 notice Shut down
> Expected results:
> Should always be able to add the new node since the queue on the original node
> in the cluster has the same capacity.

-- 
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] Resolved: (QPID-2266) error sending update: Enqueue capacity threshold exceeded

Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Conway resolved QPID-2266.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6
         Assignee: Alan Conway

Fixed in r889813

>  error sending update: Enqueue capacity threshold exceeded
> ----------------------------------------------------------
>
>                 Key: QPID-2266
>                 URL: https://issues.apache.org/jira/browse/QPID-2266
>             Project: Qpid
>          Issue Type: Bug
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.6
>
>
> From https://bugzilla.redhat.com/show_bug.cgi?id=509796
> Description of problem:
> Adding a new node to a cluster failed with a journal capacity exception.
> However the new node was using the default journal size options as was the
> existing cluster node so its not clear why this error should occur.
> Version-Release number of selected component (if applicable):
> qpidd-0.5.752581-22.el5
> rhm-0.5.3206-5.el5
> How reproducible:
> Fairly easily
> Steps to Reproduce:
> 1. start one cluster node
> 2. run  while perftest --durable true --count 50000 --size 8 --summary; do
> true; done
> 3. while this is running add a new node to the cluster, then stop it, then
> re-add it and repeat this for several times until eventually you see an error
> Actual results:
> 2009-jul-06 05:07:10 notice Journal "perftest0": Created
> 2009-jul-06 05:07:11 warning Journal "perftest0": Enqueue capacity threshold
> exceeded on queue "perftest0".
> 2009-jul-06 05:07:11 error Unexpected exception: Enqueue capacity threshold
> exceeded on queue "perftest0". (JournalImpl.cpp:576)
> 2009-jul-06 05:07:11 error Connection 10.16.44.221:46092 closed by error:
> Enqueue capacity threshold exceeded on queue "perftest0".
> (JournalImpl.cpp:576)(501)
> 2009-jul-06 05:07:11 error Channel exception: not-attached: Channel 1 is not
> attached (qpid/amqp_0_10/SessionHandler.cpp:40)
> 2009-jul-06 05:07:11 critical 10.16.44.221:19499(UPDATEE) catch-up connection
> closed prematurely 10.16.44.221:19499-1(local,catchup)
> 2009-jul-06 05:07:11 notice 10.16.44.221:19499(LEFT) leaving cluster
> grs-mrg14-test-cluster
> 2009-jul-06 05:07:11 notice Shut down
> Expected results:
> Should always be able to add the new node since the queue on the original node
> in the cluster has the same capacity.

-- 
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