On Dom, 2013-01-27 at 21:35 +0000, Fraser Adams wrote:
> I've just released an update to:
>
> https://issues.apache.org/jira/browse/QPID-3675
>
> Those of you following my recent posts over the weekend will have
> noticed that changes made in Qpid 0.20 Java Client runtime caused the
> Java QMF2 Implementation to break and thus the Qpid GUI.
>
> These changes related to how the amqp/list Content-Type is exposed to
> JMS. As it happens lists are very important for the correct behaviour of
> QMF.
>
> I've updated the QMF2 implementation to be tolerant of both the original
> BytesMessage encoding of amqp/list (so it will continue to work with
> Qpid < 0.20) plus the new Qpid 0.20 MapMessage encoding of amqp/list
> (the list items are exposed using Map keys as indices).
>
> I've also added a few features to the GUI. The main one is that it's now
> possible to disable QMF2 Events. What this means is that as well as
> selecting to have updates driven by QMF2 Event updates it's possible to
> choose a different path and get object updates triggered by a simple
> timer. The reasoning behind this is that in order to receive
> asynchronous QMF2 Events it's necessary to use AJAX "long-polling" which
> creates an HTTP connection that will block on the Server until an Event
> occurs (generally every Heartbeat, or sooner if a QMF2 Event happens).
> The problem with that approach is that if a browser only supports a
> limited number of connections the long-polling connection *could* hog
> things. If you're not interested in QMF2 asynchronous Events selecting
> Disable Events in Add QMF Console Connection disables asynchronous
> updates and forces timer polling instead. As a side-effect Connections
> created in this way will use fewer queues as the asynchronous response
> queues are no longer needed.
>
> I've also changed how the default URL is presented in the Selected QMF
> Console Connection page after Gordon noted that labelling it as simply
> "" was a bit confusing, hopefully calling it "default" and adding a note
> explaining what that means will make things a bit clearer.
>
> The latest release is qmf2-v1.1.tar.gz and can be downloaded from the
> Jira page linked above.
>
Hi Frase,
Sorry for the late reply. I've just installed version 1.1 and it shows
the following message in log:
[IoReceiver - 'my-broker-address'] INFO
org.apache.qpid.client.AMQConnection - Not a hard-error connection not
closing: org.apache.qpid.AMQException: ch=0 id=7
ExecutionException(errorCode=UNAUTHORIZED_ACCESS, commandId=14,
classCode=0, commandCode=0, fieldIndex=0,
description=unauthorized-access: authorised user id : anonymous@QPID but
user id in message declared as guest
(qpid/broker/SemanticState.cpp:484), errorInfo={}) [error code 403:
access refused]
I think that the empty string in authentication means 'anonymous' for
the Broker, but you are forcing 'guest' in messages' userId field. I
made a quick search in the code, but I was not able to do quick fix.
Regards.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
