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/21 23:17:18 UTC
[jira] Updated: (QPID-2296) Cluster errors when using
acquire-mode-not-acquired
[ https://issues.apache.org/jira/browse/QPID-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-2296:
------------------------------
Description:
Adding a new broker to a cluster while there are clients using not-acquired mode (aka "browse" mode) to retrieve messages without dequeing them can cause inconsistencies that will cause cluster members to abort. Examples of errors that may be seen as a result of this bug:
2009-12-18 10:29:04 critical cluster(20.0.100.32:23782 READY/error) local error 906715 did not occur on member 20.0.100.33:16960: resource-limit-exceeded: Policy exceeded on A_1, poli\
cy: size: max=104857600, current=952489; count: max=20000, current=20000; type=reject (../../cpp/src/qpid/broker/QueuePolicy.cpp:83)
2009-12-21 12:22:07 error Error delivering frames: local error did not occur on all cluster members : invalid-argument: anonymous.a6e88ed1-e69b-4549-b\
32d-5168f068974d: confirmed < (103+0) but only sent < (99+0) (../../cpp/src/qpid/SessionState.cpp:151) (../../cpp/src/qpid/cluster/ErrorCheck.cpp:89)
See https://bugzilla.redhat.com/show_bug.cgi?id=541927 for more details.
was:See https://bugzilla.redhat.com/show_bug.cgi?id=541927
Priority: Blocker (was: Major)
Fix Version/s: 0.6
Summary: Cluster errors when using acquire-mode-not-acquired (was: Persistent cluster problems after reboot -f )
> Cluster errors when using acquire-mode-not-acquired
> ---------------------------------------------------
>
> Key: QPID-2296
> URL: https://issues.apache.org/jira/browse/QPID-2296
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Blocker
> Fix For: 0.6
>
>
> Adding a new broker to a cluster while there are clients using not-acquired mode (aka "browse" mode) to retrieve messages without dequeing them can cause inconsistencies that will cause cluster members to abort. Examples of errors that may be seen as a result of this bug:
> 2009-12-18 10:29:04 critical cluster(20.0.100.32:23782 READY/error) local error 906715 did not occur on member 20.0.100.33:16960: resource-limit-exceeded: Policy exceeded on A_1, poli\
> cy: size: max=104857600, current=952489; count: max=20000, current=20000; type=reject (../../cpp/src/qpid/broker/QueuePolicy.cpp:83)
> 2009-12-21 12:22:07 error Error delivering frames: local error did not occur on all cluster members : invalid-argument: anonymous.a6e88ed1-e69b-4549-b\
> 32d-5168f068974d: confirmed < (103+0) but only sent < (99+0) (../../cpp/src/qpid/SessionState.cpp:151) (../../cpp/src/qpid/cluster/ErrorCheck.cpp:89)
> See https://bugzilla.redhat.com/show_bug.cgi?id=541927 for more details.
--
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