Ahh, sorry I missed that - cheers guys.
F.
On 13/07/13 10:22, Robbie Gemmell wrote:
Ken's email went to the user list as well (via CC).
Robbie
On 13 July 2013 10:13, Fraser Adams <[email protected]> wrote:
Hey Ken,
One key point is that I think it's important to get this message out on
the user list as well as the dev list, indeed I suspect it's more
important. I know that you've mentioned to Justin for the announcement
mail, but this sort of thing is good to shout about from a few different
directions.
Frase
On 12/07/13 20:17, Ken Giusti wrote:
Folks,
I've made a change on trunk to the way the C++ Broker generates
unsolicited management update messages (i.e. object update notification
messages and event messages). [1]
Previous to this change, the broker would transmit two messages for each
management event and object update - one in the old QMFv1 binary format,
and one in the QMFv2 AMQP Map format. This change disables the send of the
QMFv1 binary version of the message. The new broker default behavior is to
send only one message per event/update, in the QMFv2 map format.
The old behavior can be re-enabled, but must be done manually. This can
be done either on the qpidd command line by specifying "--mgmt-qmf1=yes",
or in the configuration file (mgmt-qmf1=yes). This command option has
existed for a while now, I've simply changed the default to "no".
And just to be clear, the remaining QMFv1 behavior has not changed: the
broker still supports QMFv1 style queries and method calls without
requiring any configuration changes.
I want this to go in for the 0.24 beta so we can get feedback sooner
rather than later. I'm hoping this acts as a "gentle nudge" that will
uncover any QMFv1 dependencies before we attempt removing any of the QMFv1
stuff in future releases.
"What does this mean to me?"
1) If you use console.py (the python QMF console library under
extras/qmf/src/py/qmf/console.**py), you'll want to upgrade to the
latest version to get the fix for this bug: https://issues.apache.org/**
jira/browse/QPID-4689 <https://issues.apache.org/jira/browse/QPID-4689> (the
version in the 0.24 beta will contain this fix)
2) If you cannot upgrade console.py, or have other code which requires
QMFv1 style updates, re-enable the old behavior as described previously
Justin - when beta is cut, we'll need to highlight this change and the
above notes in the announcement email.
This change also solves
https://issues.apache.org/**jira/browse/QPID-4907<https://issues.apache.org/jira/browse/QPID-4907>
[1]
http://svn.apache.org/viewvc?**view=revision&revision=1502642<http://svn.apache.org/viewvc?view=revision&revision=1502642>
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
[email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
[email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
