On 03/17/2010 04:43 PM, Robert Godfrey wrote:
On 16 March 2010 18:50, Gordon Sim<[email protected]> wrote:
On 03/15/2010 10:33 PM, Joan Bellver Faus wrote:
Exception in thread "Thread-3" org.apache.qpid.console.ConsoleException:
org.apache.qpid.transport.SessionException: ch=0 id=0
ExecutionException(errorCode=NOT_ALLOWED, commandId=10, classCode=7,
commandCode=1, fieldIndex=0, description=not-allowed: Exchange declared
to be of type management-topic, requested management
(qpid/broker/SessionAdapter.cpp:121), errorInfo={})
at org.apache.qpid.console.Broker.tryToConnect(Broker.java:421)
at org.apache.qpid.console.Broker.<init>(Broker.java:87)
at org.apache.qpid.console.Session.addBroker(Session.java:70)
at MMS_Example.MMS.execute(MMS.java:39)
at es.upv.dsic.gti_ia.core.BaseAgent.run(BaseAgent.java:290)
at java.lang.Thread.run(Thread.java:619)
[snip]
any idea that happens?
The type of the management exchange has been changed[1] and the java based
QMF support needs to be updated.
Why has the type been changed? Have I missed the discussion that must have
occurred before such a change was made... this change would seem to have
implications both for clients (as demonstrated here) and for others
implementing management exchanges (for instance the Java Broker).
From the commit it looks like a QMFv2 related change. I haven't been
following all the design docs around that.
However it does seem like this would break backwards compatibility for
QMFv1. Must we change the type? If this is for QMFv2 and we want to keep
QMFv1 support, it may be better to keep the old name and pick some new
ones for v2?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
