Management updates in timer create inconsistencies in a cluster. ----------------------------------------------------------------
Key: QPID-2364 URL: https://issues.apache.org/jira/browse/QPID-2364 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Alan Conway Assignee: Alan Conway Management updates are triggered by a timer. They are not predictable for the cluster and so can cause cluster shut-downs and inconsistent message delivery. We have a hack in place that suppresses exceptions when the session receives completions for transfers not yet sent (which is the usual manifestation of the unpredictability). I.e. we have in essence disabled consistency checking for management sessions. This solved immediate problems but would quickly stop working if sessions/connections could be used for management and other things (as will be more likely with QMFv2 where using management becomes quite straightforward). In a cluster, management updates need to be synchronized by executing them in the cluster dispatch thread rather than a timer thread. -- 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-subscr...@qpid.apache.org