From d490fba74749bcde972e5a0d95f84b165f8ea05e Mon Sep 17 00:00:00 2001 From: Alan Conway Date: Fri, 11 Dec 2009 20:55:45 +0000 Subject: QPID-2266: error sending update: Enqueue capacity threshold exceeded Fix for the problem with a test to verify that messages going to the store have the same headers and content-size for an updatee or a broker that receives the publish directly. git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@889813 13f79535-47bb-0310-9956-ffa450edef68 --- cpp/src/qpid/cluster/Cluster.cpp | 2 ++ 1 file changed, 2 insertions(+) (limited to 'cpp/src/qpid/cluster/Cluster.cpp') diff --git a/cpp/src/qpid/cluster/Cluster.cpp b/cpp/src/qpid/cluster/Cluster.cpp index f877720350..d049001eb0 100644 --- a/cpp/src/qpid/cluster/Cluster.cpp +++ b/cpp/src/qpid/cluster/Cluster.cpp @@ -619,6 +619,7 @@ void Cluster::initMapCompleted(Lock& l) { if (initMap.isUpdateNeeded()) { // Joining established cluster. broker.setRecovery(false); // Ditch my current store. + broker.setClusterUpdatee(true); state = JOINER; } else { // I can go ready. @@ -813,6 +814,7 @@ void Cluster::checkUpdateIn(Lock& l) { memberUpdate(l); mcast.mcastControl(ClusterReadyBody(ProtocolVersion(), myUrl.str()), self); state = CATCHUP; + broker.setClusterUpdatee(false); discarding = false; // ok to set, we're stalled for update. QPID_LOG(notice, *this << " update complete, starting catch-up."); deliverEventQueue.start(); -- cgit v1.2.1