You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Fraser Adams <fr...@blueyonder.co.uk> on 2013/01/20 17:26:18 UTC
We've got an App for that .... Qpid Web Based GUI - and more - just
released.
For those of you who follow my postings on the Qpid Mailing List you'll
probably be aware that I've been doing quite a lot with QMF2.
I've just made a fairly major uplift to the QMF2 code base.
https://issues.apache.org/jira/browse/QPID-3675
There are a few bug fixes to the core Java QMF2 implementation, the most
significant being that the ManagementAgent can return multiple partial
responses if there are large numbers of objects, the QMF2 getObjects()
call now caters for that.
However the most significant uplift is the addition of:
1) A QMF2 REST API Implementation.
2) A JavaScript QMF2 Implementation that uses the REST API as a back end.
3) A fully featured Qpid Management Web GUI that does pretty much
anything you'd need to do to
monitor and manage one or more brokers (it supports connecting to
different brokers).
The REST and JavaScript QMF2 implementations are fairly complete, the
main thing missing is support for QMF2 Query Subscriptions, which are
supported in the Java API but I've not got round to adding them to REST
& JavaScript versions.
The JavaScript implementation uses AJAX to talk to the REST API, this is
mainly because that approach is supported on pretty much every browser.
I might look to adding WebSocket support IDC when I've got a bit more
familiarity with WebSockets.
The Web GUI works on multiple browsers and is even functional on IE6
:-), it morphs quite well onto mobile devices and uses GPU accelerated
animations to give a fairly "native app" feel on iPad/iPhone.
The REST API Server was deliberately designed to have almost no
dependencies. It uses the com.sun.net.httpserver.HttpServer embedded Web
Server that is part of JDK 6 (at least on Sun and OpenJDK) so just
requires the Qpid jars on the classpath. It has been designed to make it
fairly easy to add a Servlet implementation, but that's not been done
yet as the initial goal was to make it fairly dependency free and embedded.
The REST API is very RESTful and uses PUT to add Qpid Connections but
there is automatic creation of a "default" resource if one tries to do a
GET so for example doing:
http://<host>:8080/qpid/connection/default/console/objects/queue
will retrieve the latest update of the QMF queues as a JSON string,
which will parse into a list of QmfConsoleData objects. The QpidServer
class JavaDoc documents the complete REST API but hopefully the example
above should give the gist (that's the REST equivalent of
getObjects("queue") in case it wasn't obvious).
To get up and running all that should be required is the Qpid jars on
the classpath and running ant in the root qmf2 directory.
Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
bind to the
wildcard address on the host it's running on and port 8080 though this
stuff is configurable.
Point a browser at <host>:8080 and you should be in business. By default
it will create a default QMF connection to a broker running on the same
host as the QpidRestAPI on port 5672 but the default broker connection
is configurable too.
Once running you can add QMF2 Console Connections to other brokers and
connect to them via the Web GUI.
The main limitation at the moment is the authentication. It uses basic
authentication so username/password are sent clear. I'll look to do
something better IDC but I wanted to get it released as it represents
around a years worth of work over weekends.
the authentication file is in
qmf2/bin/qpid-web/authentication/authentication.properties and has the
traditional
admin=admin
guest=guest
Obviously you might want to change that :-) it supports dynamic changes
to the file.
FWIW although the Web GUI doesn't yet have better authentication it
should be possible to configure the QpidRestAPI to use a default
connection to a secure broker. The broker credentials for the default
broker aren't returned to the browser - to use the defaults it just
supplies a broker URL of "". Obviously the broker management statistics
will still be being sent over an unsecure channel but that may not be an
issue in many cases.
It's all released under the Apache Licence and the GUI uses a JavaScript
UI library that I ended up writing as part of this project (called
itablet) which should be reusable in other projects.
I hope that this is useful to people, as I say it's taken an awful lot
of effort to put together, so I'd *really* appreciate feedback.
I should point out that this is QMF2 based and so it can only talk to
the C++ broker at the moment, however if people are interested and the
feedback is positive I'll look to uplifting the back end to also proxy
to the JMX mechanism used by the Java broker. I must admit that I've not
got any real familiarity with the Java broker, but it ought to be
do-able assuming that the Java broker JMX Management Objects have
similar capabilities to the C++ QMF Management Objects.
Finally if you point it at a broker less than 0.10 the add/delete
queue/exchange/binding features won't work as they require broker object
create/delete methods that were added in 0.10.
I've attached a couple of screen shots of a few different pages on a few
different browsers to pique your interest :-)
I really hope that the QMF stuff can make it into the main Qpid release
at some point, I did the first Java QMF2 API release over a year ago but
I've not had much feedback, hopefully with the addition of a management
GUI it'll get a bit of traction?
Best Regards,
Frase
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Bruno,
Thanks for the logs. It's very weird.
I actually copied and pasted the info from the:
ConnectionHelper.createConnection() amqp://anonymous:anonymous@QpidJMS/vhost?brokerlist='tcp://0.0.0.0:5672'
i.e. the amqp://anon............
stuff
directly into the URL part of Add QMF Console Connection and for the
anonymous-anonymous-auth-yes.txt case I definitely get "warning Failed
to retrieve sasl username" from my broker.
I'm thinking we must have different sasl configurations. If I do "sudo
sasldblistusers2" I get nothing back (I mostly mess around with --auth
no when doing dev stuff). You don't happen to have explicitly added a
user called anonymous do you??
As I say qpid-config works fine for me but I definitely get "warning
Failed to retrieve sasl username" when I try
amqp://anonymous:anonymous@QpidJMS/vhost?brokerlist='tcp://0.0.0.0:5672'
As a connection URL.
Exactly what and where SASL looks for things is Voodoo magic to me :-) I
thought it revolved around the commands sasldblistusers2, saslpasswd2.
Hmm ages back when I did mess around with auth I can vaguely recall some
weirdness I'm using Ubuntu and that doesn't have a /etc/sasl2/ directory
but does have a /etc/sasldb2 file I might have to did back an remind
myself what I did. I'm also currently running a 0.12 broker so some
stuff might have changed. I *vaguely* recall some stuff about sasl_mechs.
I was planning on upgrading to 0.20 so when I've got a moment I'll do
that and try to remember how the heck I got authentication working -
last time I tried I had a bit of a config fight, I think that the
default paths prefer Redhat/Fedora to Ubuntu...
On the other topic
> Usually qpid-tool takes some time to get all information too.
>
Now that's really interesting (AKA a slight relief....), trying
something like qpid-queue-stats would be good too. Clearly what I'm
doing and qpid-tool/qpid-queue-stats are more or less unrelated except
of course that they are both using QMF, but the code base is totally
separate - mine is Java JMS the others are python. If qpid-tool is
taking some time to get all information that would at least "suggest"
that there's something odd at your end (can you sense that's what I'm
hoping :-)). A very heavily loaded/swapping broker or something odd
network wise.
One thing I have noticed when I added a bunch of different connections
is that sometimes when I select between them the reconnection isn't as
reliable as I'd initially thought. It's only occasional, but sometimes
the broker disconnected doesn't go away. If I click back and forward
it'll generally connect and it seems OK at that point responding to real
broker disconnects. It's intermittent and TBH I only noticed it when I
added the connections with the copy'n'paste ConnectionURLs so it's going
to be a pain getting to the bottom of it - I *hate* intermittent bugs :-)
The reconnection stuff is pretty complicated and subtle and switching
the "active" connection between different URLs was one of the most
recent bits I added. It ought to be unrelated to the things you're
describing but it's something to watch out for. It's easy to work around
though by clicking the previous connection and back again.
F.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
I send the logs from both guest/guest and anonymous/anonymous versions
of qmfv2-1.1 with and without authentication.
More inline:
On Sex, 2013-02-01 at 12:16 +0000, Fraser Adams wrote:
> I'm not totally sure what you mean by what you've said below :-/
>
> As I say I've tried with settings that should create a Java
> ConnectionURL with anonymous:anonymous at the start, which ought to be
> the same as you changing the ConnectionHelper username/password Strings
> from guest to anonymous but I'm seeing "warning Failed to retrieve sasl
> username" when I do.
>
> I can't quite reconcile what you reckon you're seeing with what I'm
> seeing. What I'm seeing would seem to align with what Pavel covered in
> the Jira he mentioned.
>
> I don't think this is sasl per se, because if I use plain old
> qpid-config that would connect to localhost:5672 as anonymous and I
> don't get the warning, so it seems to be how Java ConnectionURLs are
> handled.
>
> Were you able to enable logging and pull out the URL ConnectionHelper
> created to give to the underlying ConnectionFactory?
>
>
>
> On a different note I'm still struggling to figure out why your data
> updates might be sluggish/unreliable. You mentioned you're using Chrome
> - that's normally pretty well behaved and supports a decent number of
> HTTP connections. I tried Chrome on a netbook to my REST Server and it
> behaved perfectly.
I've not reached there after my testing reset. Will be my next step.
>
>
> Is there anything unusual about your network/topology etc. At this stage
> it'd be good if you could go back to basics and work out from there.
> Would you be able to try running up a broker on the same host as
> QpidRestAPI with --auth no then working out from there adding auth and
> moving out to the brokers you actually care about?
Yes, I'll start from a simple configuration.
>
> I'm afraid that all the dev on this has been done in my spare time and
> my home network has only got one Linux server, though I've tried a ton
> of browsers and I've got a fairly big WiFi set up with two Access Points
> and haven't seen issues even using avahi so my server has a sensible
> name on my private network. But I've not been able to try QpidRestAPI
> and the broker on different hosts.
>
> I can't think of any *obvious* reasons why there should be any problems
> though because the underlying QMF2 stuff is really just a JMS client, so
> if you have QMF problems between two hosts then I'd expect any other
> Qpid application would behave equally weirdly. As a thought what happens
> if you run qpid-queue-stats on the host you're running QpidRestAPI on
> and pointing that to the broker in question. That's *really* worth
> checking because qpid-queue-stats gets data pushed by the broker
> periodically.
Usually qpid-tool takes some time to get all information too.
>
> I assume you've checked that any network you have between the hosts
> behaves normally for everything else? Probably not relevant, but I once
> had a NIC that was a bit flaky and ended negotiating a half duplex link
> - imagine my surprise :-)
It's my testing broker, even for performance, so it should be fine.
>
> How heavily loaded is the broker that you are talking to when your
> updates are sluggish? The updates are every 10s and pull back more or
> less every QMF statistic serialising to JSON. I've tested with > 500
> connections plus queues and bindings. Bear in mind when you get to this
> sort of number transfers might get to the MB size given the number of
> properties in queues, but unless you're on a really low bandwidth link
> you shouldn't notice that. On my setup top on Firefox was pretty modest
> doing that.
It could be with high load when I tested, I will test again.
>
> However if you are really trashing the broker too you might see quirks I
> set up queues that were far too big and connected slow consumers + fast
> producers and when my broker went in to swap unsurprisingly I'd see
> update glitches - but really the only time I've had anything other than
> regular updates was when I pushed the broker into swap - so I remain
> befuddled :-(
>
>
> You didn't get back to me on this but you really really haven't got
> --mgmt-pub-interval set to anything other than the default have you??
No, it's set to 10 (default).
>
> If you look on the "broker" page on the GUI it'll be down as
> mgmtPubInterval. If you look at the uptime mine increments by 10 seconds
> every 10 seconds are you seeing any sort of periodicity?
I'll look at it in my next test.
>
> Have you taken a look at the graphs for the QMF Queues, the one bound to
> qmf.default.direct and indeed the graph for that exchange ought to be
> quite spiky/noisy. Looking at that graph you should be able to see when
> your statistics updates are arriving.
Not yet, but I will.
>
> I'm afraid I'm struggling to come up with answers on this, I'd be really
> interested to know what others are experiencing.
>
> Frase
Regards.
>
>
> On 01/02/13 11:10, Bruno Matos wrote:
> > Hi Fraser,
> >
> > I think the default sasl configuration will accept anything as the
> > username, it only forces the UserID of the message to be the same as the
> > authentication's username.
> >
> > Regards.
> >
> > On Ter, 2013-01-29 at 19:04 +0000, Fraser Adams wrote:
> >> Hi Bruno,
> >> are you *sure* that this worked?
> >>
> >> So I've literally just tried a basic JMS consumer with a broker fired up
> >> with qpidd (e.g. authentication enabled) and I used a ConnectionURL
> >>
> >> connectionfactory.ConnectionFactory =
> >> amqp://anonymous:anonymous@clientid/test?brokerlist='tcp://localhost:5672'
> >>
> >> and my broker said:
> >>
> >> 2013-01-29 18:51:01 warning Failed to retrieve sasl username
> >>
> >>
> >> Similarly if I add a URL of "anonymous/anonymous@localhost:5672" in the
> >> GUI my broker says the same. This latter case creates a Java
> >> ConnectionURL the same as my standalone JMS consumer mentioned above.
> >>
> >> If I do qpidd --auth no it works fine, but not with authentication enabled.
> >>
> >> If you enable log notice in the log4j.xml I think that ConnectionHelper
> >> (in v1.1 anyway) spits out the Java ConnectionURL it created so it'd be
> >> interesting to see what that says and if you could also confirm you
> >> really did use the default this time (you didn't disable auth in config)
> >>
> >> What you appear to be seeing all seems a bit odd, especially given
> >> Pavel's mail about the outstanding bug, and as I say it's inconsistent
> >> with what I've just seen, so I'm a bit baffled...
> >>
> >> Frase
> >>
> >>> I changed the default username and password to anonymous in
> >>> ConnectionHelper.java:569, and it works for now. I don't know the
> >>> difference between guest/guest and anonymous/anonymous, usually I work
> >>> with authentication.
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> >> For additional commands, e-mail: users-help@qpid.apache.org
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
--
Bruno Matos
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
I'm not totally sure what you mean by what you've said below :-/
As I say I've tried with settings that should create a Java
ConnectionURL with anonymous:anonymous at the start, which ought to be
the same as you changing the ConnectionHelper username/password Strings
from guest to anonymous but I'm seeing "warning Failed to retrieve sasl
username" when I do.
I can't quite reconcile what you reckon you're seeing with what I'm
seeing. What I'm seeing would seem to align with what Pavel covered in
the Jira he mentioned.
I don't think this is sasl per se, because if I use plain old
qpid-config that would connect to localhost:5672 as anonymous and I
don't get the warning, so it seems to be how Java ConnectionURLs are
handled.
Were you able to enable logging and pull out the URL ConnectionHelper
created to give to the underlying ConnectionFactory?
On a different note I'm still struggling to figure out why your data
updates might be sluggish/unreliable. You mentioned you're using Chrome
- that's normally pretty well behaved and supports a decent number of
HTTP connections. I tried Chrome on a netbook to my REST Server and it
behaved perfectly.
Is there anything unusual about your network/topology etc. At this stage
it'd be good if you could go back to basics and work out from there.
Would you be able to try running up a broker on the same host as
QpidRestAPI with --auth no then working out from there adding auth and
moving out to the brokers you actually care about?
I'm afraid that all the dev on this has been done in my spare time and
my home network has only got one Linux server, though I've tried a ton
of browsers and I've got a fairly big WiFi set up with two Access Points
and haven't seen issues even using avahi so my server has a sensible
name on my private network. But I've not been able to try QpidRestAPI
and the broker on different hosts.
I can't think of any *obvious* reasons why there should be any problems
though because the underlying QMF2 stuff is really just a JMS client, so
if you have QMF problems between two hosts then I'd expect any other
Qpid application would behave equally weirdly. As a thought what happens
if you run qpid-queue-stats on the host you're running QpidRestAPI on
and pointing that to the broker in question. That's *really* worth
checking because qpid-queue-stats gets data pushed by the broker
periodically.
I assume you've checked that any network you have between the hosts
behaves normally for everything else? Probably not relevant, but I once
had a NIC that was a bit flaky and ended negotiating a half duplex link
- imagine my surprise :-)
How heavily loaded is the broker that you are talking to when your
updates are sluggish? The updates are every 10s and pull back more or
less every QMF statistic serialising to JSON. I've tested with > 500
connections plus queues and bindings. Bear in mind when you get to this
sort of number transfers might get to the MB size given the number of
properties in queues, but unless you're on a really low bandwidth link
you shouldn't notice that. On my setup top on Firefox was pretty modest
doing that.
However if you are really trashing the broker too you might see quirks I
set up queues that were far too big and connected slow consumers + fast
producers and when my broker went in to swap unsurprisingly I'd see
update glitches - but really the only time I've had anything other than
regular updates was when I pushed the broker into swap - so I remain
befuddled :-(
You didn't get back to me on this but you really really haven't got
--mgmt-pub-interval set to anything other than the default have you??
If you look on the "broker" page on the GUI it'll be down as
mgmtPubInterval. If you look at the uptime mine increments by 10 seconds
every 10 seconds are you seeing any sort of periodicity?
Have you taken a look at the graphs for the QMF Queues, the one bound to
qmf.default.direct and indeed the graph for that exchange ought to be
quite spiky/noisy. Looking at that graph you should be able to see when
your statistics updates are arriving.
I'm afraid I'm struggling to come up with answers on this, I'd be really
interested to know what others are experiencing.
Frase
On 01/02/13 11:10, Bruno Matos wrote:
> Hi Fraser,
>
> I think the default sasl configuration will accept anything as the
> username, it only forces the UserID of the message to be the same as the
> authentication's username.
>
> Regards.
>
> On Ter, 2013-01-29 at 19:04 +0000, Fraser Adams wrote:
>> Hi Bruno,
>> are you *sure* that this worked?
>>
>> So I've literally just tried a basic JMS consumer with a broker fired up
>> with qpidd (e.g. authentication enabled) and I used a ConnectionURL
>>
>> connectionfactory.ConnectionFactory =
>> amqp://anonymous:anonymous@clientid/test?brokerlist='tcp://localhost:5672'
>>
>> and my broker said:
>>
>> 2013-01-29 18:51:01 warning Failed to retrieve sasl username
>>
>>
>> Similarly if I add a URL of "anonymous/anonymous@localhost:5672" in the
>> GUI my broker says the same. This latter case creates a Java
>> ConnectionURL the same as my standalone JMS consumer mentioned above.
>>
>> If I do qpidd --auth no it works fine, but not with authentication enabled.
>>
>> If you enable log notice in the log4j.xml I think that ConnectionHelper
>> (in v1.1 anyway) spits out the Java ConnectionURL it created so it'd be
>> interesting to see what that says and if you could also confirm you
>> really did use the default this time (you didn't disable auth in config)
>>
>> What you appear to be seeing all seems a bit odd, especially given
>> Pavel's mail about the outstanding bug, and as I say it's inconsistent
>> with what I've just seen, so I'm a bit baffled...
>>
>> Frase
>>
>>> I changed the default username and password to anonymous in
>>> ConnectionHelper.java:569, and it works for now. I don't know the
>>> difference between guest/guest and anonymous/anonymous, usually I work
>>> with authentication.
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
Hi Fraser,
I think the default sasl configuration will accept anything as the
username, it only forces the UserID of the message to be the same as the
authentication's username.
Regards.
On Ter, 2013-01-29 at 19:04 +0000, Fraser Adams wrote:
> Hi Bruno,
> are you *sure* that this worked?
>
> So I've literally just tried a basic JMS consumer with a broker fired up
> with qpidd (e.g. authentication enabled) and I used a ConnectionURL
>
> connectionfactory.ConnectionFactory =
> amqp://anonymous:anonymous@clientid/test?brokerlist='tcp://localhost:5672'
>
> and my broker said:
>
> 2013-01-29 18:51:01 warning Failed to retrieve sasl username
>
>
> Similarly if I add a URL of "anonymous/anonymous@localhost:5672" in the
> GUI my broker says the same. This latter case creates a Java
> ConnectionURL the same as my standalone JMS consumer mentioned above.
>
> If I do qpidd --auth no it works fine, but not with authentication enabled.
>
> If you enable log notice in the log4j.xml I think that ConnectionHelper
> (in v1.1 anyway) spits out the Java ConnectionURL it created so it'd be
> interesting to see what that says and if you could also confirm you
> really did use the default this time (you didn't disable auth in config)
>
> What you appear to be seeing all seems a bit odd, especially given
> Pavel's mail about the outstanding bug, and as I say it's inconsistent
> with what I've just seen, so I'm a bit baffled...
>
> Frase
>
> > I changed the default username and password to anonymous in
> > ConnectionHelper.java:569, and it works for now. I don't know the
> > difference between guest/guest and anonymous/anonymous, usually I work
> > with authentication.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Bruno,
are you *sure* that this worked?
So I've literally just tried a basic JMS consumer with a broker fired up
with qpidd (e.g. authentication enabled) and I used a ConnectionURL
connectionfactory.ConnectionFactory =
amqp://anonymous:anonymous@clientid/test?brokerlist='tcp://localhost:5672'
and my broker said:
2013-01-29 18:51:01 warning Failed to retrieve sasl username
Similarly if I add a URL of "anonymous/anonymous@localhost:5672" in the
GUI my broker says the same. This latter case creates a Java
ConnectionURL the same as my standalone JMS consumer mentioned above.
If I do qpidd --auth no it works fine, but not with authentication enabled.
If you enable log notice in the log4j.xml I think that ConnectionHelper
(in v1.1 anyway) spits out the Java ConnectionURL it created so it'd be
interesting to see what that says and if you could also confirm you
really did use the default this time (you didn't disable auth in config)
What you appear to be seeing all seems a bit odd, especially given
Pavel's mail about the outstanding bug, and as I say it's inconsistent
with what I've just seen, so I'm a bit baffled...
Frase
> I changed the default username and password to anonymous in
> ConnectionHelper.java:569, and it works for now. I don't know the
> difference between guest/guest and anonymous/anonymous, usually I work
> with authentication.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
Hi Fraser,
On Seg, 2013-01-28 at 21:08 +0000, Fraser Adams wrote:
> Hi Bruno,
> Yes that's exactly what I thought was happening too.....
>
> Please do take a look at some of the other posts I've made to the
> mailing list over the last few days.
>
> I made a post entitled "Could somebody *please* explain Java Connection
> URLs" to which Pavel Moravec kindly replied:
>
> "
>
> Hi Fraser,
> there is a bug in Java client disallowing no credentials option, seehttps://issues.apache.org/jira/browse/QPID-3396.
>
> Kind regards,
> Pavel
> "
>
> As you may have gathered the "back end" part of the GUI is the
> QpidRestAPI written in Java. You may or may not know this but Java has a
> particular ConnectionURL format documented here:
>
> http://qpid.apache.org/books/0.20/Programming-In-Apache-Qpid/html/QpidJNDI.html#section-jms-connection-url
>
> They aren't erm the "most convenient" form to do things with so what I
> did was to write a helper class called "ConnectionHelper" that can take
> URLs in all the main formats - the Java one just gets passed through,
> the one used by the python tools (guest/guest@host:port) and the amqp
> URL used in qpid::messaging should all work and the Class basically
> constructs a Java form Connection URL to pass to JNDI.
>
> Anyways as you've observed if no username/password is supplied this
> defaults to amqp://guest:guest@...... when I saw your last post I
> clocked that and took a closer look.
>
> The spec says
> "amqp://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]"
> so the user/pass *should* be optional, however unfortunately it's not.
>
> I actually started writing that bit an age back ~18 months and I got
> bitten then and forgot about it until your post. I had another go trying
> different approaches, but if you look at my posting there's basically
> currently no way in Java to specify a user ID on anonymous (well no way
> that I've come across and nobody apart from Pavel replied to my post so
> I'm assuming that there won't be a way until that bug is fixed).
>
> So from the perspective of my code I'm not sure that there's much I can
> do unless someone can suggest a Connection URL for connecting as
> anonymous - if they can I'll happily change the code to support that.
>
> All I can suggest for the moment if you want to use --auth yes is to add
> a "guest" user in SASL, or better yet a real username/password - TBH if
> you're not doing that you might as well use --auth no.
I changed the default username and password to anonymous in
ConnectionHelper.java:569, and it works for now. I don't know the
difference between guest/guest and anonymous/anonymous, usually I work
with authentication.
>
> I hope that this doesn't seem to be a cop-out, I've genuinely tried to
> come up with something - in between getting it to work on Qpid 0.20 :-(
>
> One possibility is for me to take a look at the patch mentioned in
> Pavel's response. It might be possible for me to create a Connection
> using the Qpid specific implementation classes rather than constructing
> a Connection URL and using the ConnectionFactory. It's not ideal but I
> suspect that it might work, but then I'll be a bit at the beck and call
> if someone tinkers around with those.
>
>
> As an aside you didn't give me any info on the browser you were using
> etc. I still can't think of any reason why it'd take as long as you've
> been suggesting to get updates to queues/exchanges etc. Have you tried
> the new option I've added to disable QMF Events. That switch basically
> switches that particular connection to use timed polling for updates
> instead of receiving Events and using heartbeats to trigger updates.
> Because the async event approach uses AJAX long-polling which "hogs" an
> HTTP connection if you've got a browser with limited connections
> available disabling QMF Events and using a timer driven poll just might
> be more responsive.
>
> It was just a hunch really, but if neither approach give updates pretty
> regularly every 10 seconds then I'd point the finger at something
> network related on your end. I've never experience the sort of symptoms
> you described and I'd be most interested to hear from others. I'm afraid
> that I can't think what it could be other than I've posted here.
>
> Regards,
> Frase
>
> > 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.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
Regards.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: Qpid GUI config - response for SergeyZhemzhitsky
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hi Frase,
I have no chance to test the GUI with mobile browser yet, but screenshots you attached are really cool.
I suppose it's the best web-based qpid management tool by the time!
Best Regards,
Sergey Zhemzhitsky
Phone. +7 495 2580500 ext. 1246
-----Original Message-----
From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
Sent: Monday, February 04, 2013 11:07 PM
To: users@qpid.apache.org
Subject: Re: Qpid GUI config - response for SergeyZhemzhitsky
Hey wow Sergey,
I'm so pleased that you gave it a whirl :-) I guess that the instructions were clear enough after all, cool!
Hopefully the code is fairly OK to follow. It looks a bit daunting at first, but it's actually fairly well structured (well I think so :-)) - basically there's a Singleton class for each core page and they are mostly pretty self contained. Any data passed between "pages" gets attached to the query part of the url and the core navigation is done via url fragments/hash which map nicely to DIV ids.
I've tried to put in a decent amount of comments in a JavaDoc style, of course you can never have too many comments, but hopefully what's there is useful. I'm toying with the idea of adding a JavaScript minimiser on the server to minimise "on the fly" so it's not so verbose when sent over the wire, but that's a "nice to have" for now.
I actually quite like that approach to implementing the config, it was one of those "lightbulb" moments to do something pretty useful trivially easily.
One thing to be aware of is that clicking between the different connections isn't as reliable as it ought to be in v1.1 :-( It was a feature I added a bit late in the day and to be honest I also rushed in the feature to disable QMF Events (and use timed polling instead).
Having added the config.js I had a lot more connections to play with and noticed that sometimes a connection would flag up Broker Disconnected and not reconnect. I also noticed that if I randomly clicked between them quickly I may get extra connections staying active and occasionally they haven't expired.
I spent the weekend going through the JavaScript and REST object lifecycle and adding a lot more defensive code. I think that I've sorted that stuff out now so hopefully the next release should be a little less flaky. To be fair I've always been able to connect, but sometimes I've had to click back and forth between connections, which is a bit rubbish.
Anyway hopefully that's another bug shot.
Thanks again for playing with the GUI and for trying out the config.js I hope that you are liking it. Niggles aside I'm mostly pretty pleased with it. I really hope that it can be used to "show off" Qpid to "management types". Have you been able to try it with a mobile browser yet? It looks pretty nice on an iPhone :-)
Cheers,
Frase
On 04/02/13 12:53, Zhemzhitsky Sergey wrote:
> Hello Frase,
>
> config.js with consoleConnections works like a charm.
>
> Now it's possible to monitor multiple brokers without explicitly defining qmf connections to them by means of GUI.
>
> Great job! Thanks a lot!
>
> Best Regards,
> Sergey
>
> -----Original Message-----
> From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
> Sent: Saturday, February 02, 2013 8:17 PM
> To: users@qpid.apache.org
> Subject: Qpid GUI config - response for SergeyZhemzhitsky
>
> Hi Sergey,
> Since we last spoke I had a think about this and a bit of a play and
> I've come up with what I reckon is quite an elegant and simple
> approach to this, which also "embraces the power of the client side"
> which follows the spirit of this GUI :-)
>
>
> To explain a bit. As I mentioned in my original response the QpidRestAPI server is intended to be a fairly "thin" layer. Conceptually what I was trying to achieve was the concept that the *browser* behaves as a proper QMF Console. What this means is that if you imagine say a python client like qpid-config creating a Qpid Connection then a Console object and using that to get QMF Objects that's exactly what I'm getting the browser to do.
>
> In practice it's not "quite" as simple as that given network restrictions in the browser, so what actually happens is that when I create a Qpid Connection in the browser "under the hood" it does a RESTful PUT to PUT a Qpid Connection resource onto the REST Server (in other words when a Connection is created in JavaScript that results in a proxy connection getting created on the QpidRestAPI) once in place that resource is controlled via RESTful GET/POST and eventually DELETE methods invoked via jQuery AJAX calls.
>
> That happens independently for any browser connecting, so although the Connection objects have resource "names" on QpidRestAPI they are best thought of as "handles" and entirely different to the Connection names on the GUI, which are intended to be memorable/friendly names for connections and entirely up to the user. The JavaScript Connection class actually creates a UUID for the "handle" transparent to the user.
>
>
> So that's just explaining how the architecture works, but in terms of simple config - well as it happens in the JavaScript qmfui.Console class there was a variable called consoleConnections which was used to hold the array of consoleConnections added in the GUI and this was initialised to hold the default.
>
> Just to mess around I made this a public property of qmfui.Console e.g.
>
> this.consoleConnections = [{name: "default", url: "",
> connectionOptions: ""}];
>
> instead of
>
> var consoleConnections = [{name: "default", url: "",
> connectionOptions: ""}];
>
>
> So why that's significant is it can be used to provide trivially
> simple configuration as ultimately it's just a JSON array, so I added
> the following line to qmf.html in the ui subdirectory (this has to be
> after the line <script src="/qmf-ui/scripts/qmf-ui.js"></script> in
> the head
> block)
>
> <script src="/ui/config.js"></script>
>
> and added the file config.js to the ui subdirectory too (same
> directory as the html). In this file I put:
>
>
> qmfui.Console.consoleConnections = [
> {name: "default", url: "", connectionOptions: ""},
> {name: "localhost", url: "localhost:5672", connectionOptions: ""},
> {name: "wildcard", url: "0.0.0.0:5672", connectionOptions: ""}
> ];
>
>
> As you can see it's a fairly straightforward JSON array containing
> JSON objects describing the connections you'd like to start out with.
>
> If you don't want anything other than the default just leave config.js
> empty.
>
> This is really serving config to the client side, but that's where all
> the state is held so it makes a lot more sense than properties on the
> server.
>
>
> The reason I've put the config.js in the ui subdirectory is because
> that one is "protected" by the authentication. At the moment I've only
> got support for BasicAuthentication so user/passwd are sent clear and
> be aware so to would config.js. If you have sensitive
> usernames/passwords that's something to be aware of if you want to use
> this config at the moment.
>
> For the case of the default URL "" that doesn't get passed to the
> browser so you could configure a broker with a user/pass using
> ./QpidRestAPI -a ...... and that info wouldn't be passed to the
> browser because the browser only needs to supply a url of "" to create
> a connection using the default connection URL.
>
> It might not be an issue if you're on a private network, but do bear
> it in mind. Providing a bit more security is on my "todo" list but it
> wasn't top of my priorities initially.
>
>
> I'll incorporate this stuff into my next release, but as you asked
> about this feature I thought that you might be interested - if you're
> feeling adventurous you could could tweak your own copy of qmf-ui.js -
> if you search for "consoleConnections" in there it's really just a
> case of changing "var " to "this." in front of it then adding the
> tweak to qmf.html and adding the config.js I describe above.
>
> Let me know how you get on...
>
> Best Regards,
> Frase
>
>
>
> On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
>> Hi Fraser,
>>
>> Amazing GUI! Thanks a lot!
>>
>> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>>
>> config.properties
>>
>> broker.default=guest/guest@host1:5672
>> broker.name2=guest/guest@host2:5672
>> broker.name3=guest/guest@host3:5672
>>
>> broker.default.hide.qmf.objects=true
>> broker.name2.hide.qmf.objects=false
>> broker.name3.hide.qmf.objects=true
>>
>> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>>
>>
>> Best Regards,
>> Sergey
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For
> additional commands, e-mail: users-help@qpid.apache.org
>
>
> _______________________________________________________
> CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For
> additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid GUI config - response for SergeyZhemzhitsky
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hey wow Sergey,
I'm so pleased that you gave it a whirl :-) I guess that the
instructions were clear enough after all, cool!
Hopefully the code is fairly OK to follow. It looks a bit daunting at
first, but it's actually fairly well structured (well I think so :-)) -
basically there's a Singleton class for each core page and they are
mostly pretty self contained. Any data passed between "pages" gets
attached to the query part of the url and the core navigation is done
via url fragments/hash which map nicely to DIV ids.
I've tried to put in a decent amount of comments in a JavaDoc style, of
course you can never have too many comments, but hopefully what's there
is useful. I'm toying with the idea of adding a JavaScript minimiser on
the server to minimise "on the fly" so it's not so verbose when sent
over the wire, but that's a "nice to have" for now.
I actually quite like that approach to implementing the config, it was
one of those "lightbulb" moments to do something pretty useful trivially
easily.
One thing to be aware of is that clicking between the different
connections isn't as reliable as it ought to be in v1.1 :-( It was a
feature I added a bit late in the day and to be honest I also rushed in
the feature to disable QMF Events (and use timed polling instead).
Having added the config.js I had a lot more connections to play with and
noticed that sometimes a connection would flag up Broker Disconnected
and not reconnect. I also noticed that if I randomly clicked between
them quickly I may get extra connections staying active and occasionally
they haven't expired.
I spent the weekend going through the JavaScript and REST object
lifecycle and adding a lot more defensive code. I think that I've sorted
that stuff out now so hopefully the next release should be a little less
flaky. To be fair I've always been able to connect, but sometimes I've
had to click back and forth between connections, which is a bit rubbish.
Anyway hopefully that's another bug shot.
Thanks again for playing with the GUI and for trying out the config.js I
hope that you are liking it. Niggles aside I'm mostly pretty pleased
with it. I really hope that it can be used to "show off" Qpid to
"management types". Have you been able to try it with a mobile browser
yet? It looks pretty nice on an iPhone :-)
Cheers,
Frase
On 04/02/13 12:53, Zhemzhitsky Sergey wrote:
> Hello Frase,
>
> config.js with consoleConnections works like a charm.
>
> Now it's possible to monitor multiple brokers without explicitly defining qmf connections to them by means of GUI.
>
> Great job! Thanks a lot!
>
> Best Regards,
> Sergey
>
> -----Original Message-----
> From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
> Sent: Saturday, February 02, 2013 8:17 PM
> To: users@qpid.apache.org
> Subject: Qpid GUI config - response for SergeyZhemzhitsky
>
> Hi Sergey,
> Since we last spoke I had a think about this and a bit of a play and I've come up with what I reckon is quite an elegant and simple approach to this, which also "embraces the power of the client side" which follows the spirit of this GUI :-)
>
>
> To explain a bit. As I mentioned in my original response the QpidRestAPI server is intended to be a fairly "thin" layer. Conceptually what I was trying to achieve was the concept that the *browser* behaves as a proper QMF Console. What this means is that if you imagine say a python client like qpid-config creating a Qpid Connection then a Console object and using that to get QMF Objects that's exactly what I'm getting the browser to do.
>
> In practice it's not "quite" as simple as that given network restrictions in the browser, so what actually happens is that when I create a Qpid Connection in the browser "under the hood" it does a RESTful PUT to PUT a Qpid Connection resource onto the REST Server (in other words when a Connection is created in JavaScript that results in a proxy connection getting created on the QpidRestAPI) once in place that resource is controlled via RESTful GET/POST and eventually DELETE methods invoked via jQuery AJAX calls.
>
> That happens independently for any browser connecting, so although the Connection objects have resource "names" on QpidRestAPI they are best thought of as "handles" and entirely different to the Connection names on the GUI, which are intended to be memorable/friendly names for connections and entirely up to the user. The JavaScript Connection class actually creates a UUID for the "handle" transparent to the user.
>
>
> So that's just explaining how the architecture works, but in terms of simple config - well as it happens in the JavaScript qmfui.Console class there was a variable called consoleConnections which was used to hold the array of consoleConnections added in the GUI and this was initialised to hold the default.
>
> Just to mess around I made this a public property of qmfui.Console e.g.
>
> this.consoleConnections = [{name: "default", url: "",
> connectionOptions: ""}];
>
> instead of
>
> var consoleConnections = [{name: "default", url: "",
> connectionOptions: ""}];
>
>
> So why that's significant is it can be used to provide trivially simple
> configuration as ultimately it's just a JSON array, so I added the
> following line to qmf.html in the ui subdirectory (this has to be after
> the line <script src="/qmf-ui/scripts/qmf-ui.js"></script> in the head
> block)
>
> <script src="/ui/config.js"></script>
>
> and added the file config.js to the ui subdirectory too (same directory
> as the html). In this file I put:
>
>
> qmfui.Console.consoleConnections = [
> {name: "default", url: "", connectionOptions: ""},
> {name: "localhost", url: "localhost:5672", connectionOptions: ""},
> {name: "wildcard", url: "0.0.0.0:5672", connectionOptions: ""}
> ];
>
>
> As you can see it's a fairly straightforward JSON array containing JSON
> objects describing the connections you'd like to start out with.
>
> If you don't want anything other than the default just leave config.js
> empty.
>
> This is really serving config to the client side, but that's where all
> the state is held so it makes a lot more sense than properties on the
> server.
>
>
> The reason I've put the config.js in the ui subdirectory is because that
> one is "protected" by the authentication. At the moment I've only got
> support for BasicAuthentication so user/passwd are sent clear and be
> aware so to would config.js. If you have sensitive usernames/passwords
> that's something to be aware of if you want to use this config at the
> moment.
>
> For the case of the default URL "" that doesn't get passed to the
> browser so you could configure a broker with a user/pass using
> ./QpidRestAPI -a ...... and that info wouldn't be passed to the browser
> because the browser only needs to supply a url of "" to create a
> connection using the default connection URL.
>
> It might not be an issue if you're on a private network, but do bear it
> in mind. Providing a bit more security is on my "todo" list but it
> wasn't top of my priorities initially.
>
>
> I'll incorporate this stuff into my next release, but as you asked about
> this feature I thought that you might be interested - if you're feeling
> adventurous you could could tweak your own copy of qmf-ui.js - if you
> search for "consoleConnections" in there it's really just a case of
> changing "var " to "this." in front of it then adding the tweak to
> qmf.html and adding the config.js I describe above.
>
> Let me know how you get on...
>
> Best Regards,
> Frase
>
>
>
> On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
>> Hi Fraser,
>>
>> Amazing GUI! Thanks a lot!
>>
>> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>>
>> config.properties
>>
>> broker.default=guest/guest@host1:5672
>> broker.name2=guest/guest@host2:5672
>> broker.name3=guest/guest@host3:5672
>>
>> broker.default.hide.qmf.objects=true
>> broker.name2.hide.qmf.objects=false
>> broker.name3.hide.qmf.objects=true
>>
>> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>>
>>
>> Best Regards,
>> Sergey
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
> _______________________________________________________
> CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: Qpid GUI config - response for SergeyZhemzhitsky
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hello Frase,
config.js with consoleConnections works like a charm.
Now it's possible to monitor multiple brokers without explicitly defining qmf connections to them by means of GUI.
Great job! Thanks a lot!
Best Regards,
Sergey
-----Original Message-----
From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
Sent: Saturday, February 02, 2013 8:17 PM
To: users@qpid.apache.org
Subject: Qpid GUI config - response for SergeyZhemzhitsky
Hi Sergey,
Since we last spoke I had a think about this and a bit of a play and I've come up with what I reckon is quite an elegant and simple approach to this, which also "embraces the power of the client side" which follows the spirit of this GUI :-)
To explain a bit. As I mentioned in my original response the QpidRestAPI server is intended to be a fairly "thin" layer. Conceptually what I was trying to achieve was the concept that the *browser* behaves as a proper QMF Console. What this means is that if you imagine say a python client like qpid-config creating a Qpid Connection then a Console object and using that to get QMF Objects that's exactly what I'm getting the browser to do.
In practice it's not "quite" as simple as that given network restrictions in the browser, so what actually happens is that when I create a Qpid Connection in the browser "under the hood" it does a RESTful PUT to PUT a Qpid Connection resource onto the REST Server (in other words when a Connection is created in JavaScript that results in a proxy connection getting created on the QpidRestAPI) once in place that resource is controlled via RESTful GET/POST and eventually DELETE methods invoked via jQuery AJAX calls.
That happens independently for any browser connecting, so although the Connection objects have resource "names" on QpidRestAPI they are best thought of as "handles" and entirely different to the Connection names on the GUI, which are intended to be memorable/friendly names for connections and entirely up to the user. The JavaScript Connection class actually creates a UUID for the "handle" transparent to the user.
So that's just explaining how the architecture works, but in terms of simple config - well as it happens in the JavaScript qmfui.Console class there was a variable called consoleConnections which was used to hold the array of consoleConnections added in the GUI and this was initialised to hold the default.
Just to mess around I made this a public property of qmfui.Console e.g.
this.consoleConnections = [{name: "default", url: "",
connectionOptions: ""}];
instead of
var consoleConnections = [{name: "default", url: "",
connectionOptions: ""}];
So why that's significant is it can be used to provide trivially simple
configuration as ultimately it's just a JSON array, so I added the
following line to qmf.html in the ui subdirectory (this has to be after
the line <script src="/qmf-ui/scripts/qmf-ui.js"></script> in the head
block)
<script src="/ui/config.js"></script>
and added the file config.js to the ui subdirectory too (same directory
as the html). In this file I put:
qmfui.Console.consoleConnections = [
{name: "default", url: "", connectionOptions: ""},
{name: "localhost", url: "localhost:5672", connectionOptions: ""},
{name: "wildcard", url: "0.0.0.0:5672", connectionOptions: ""}
];
As you can see it's a fairly straightforward JSON array containing JSON
objects describing the connections you'd like to start out with.
If you don't want anything other than the default just leave config.js
empty.
This is really serving config to the client side, but that's where all
the state is held so it makes a lot more sense than properties on the
server.
The reason I've put the config.js in the ui subdirectory is because that
one is "protected" by the authentication. At the moment I've only got
support for BasicAuthentication so user/passwd are sent clear and be
aware so to would config.js. If you have sensitive usernames/passwords
that's something to be aware of if you want to use this config at the
moment.
For the case of the default URL "" that doesn't get passed to the
browser so you could configure a broker with a user/pass using
./QpidRestAPI -a ...... and that info wouldn't be passed to the browser
because the browser only needs to supply a url of "" to create a
connection using the default connection URL.
It might not be an issue if you're on a private network, but do bear it
in mind. Providing a bit more security is on my "todo" list but it
wasn't top of my priorities initially.
I'll incorporate this stuff into my next release, but as you asked about
this feature I thought that you might be interested - if you're feeling
adventurous you could could tweak your own copy of qmf-ui.js - if you
search for "consoleConnections" in there it's really just a case of
changing "var " to "this." in front of it then adding the tweak to
qmf.html and adding the config.js I describe above.
Let me know how you get on...
Best Regards,
Frase
On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
> Hi Fraser,
>
> Amazing GUI! Thanks a lot!
>
> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>
> config.properties
>
> broker.default=guest/guest@host1:5672
> broker.name2=guest/guest@host2:5672
> broker.name3=guest/guest@host3:5672
>
> broker.default.hide.qmf.objects=true
> broker.name2.hide.qmf.objects=false
> broker.name3.hide.qmf.objects=true
>
> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>
>
> Best Regards,
> Sergey
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
Qpid GUI config - response for SergeyZhemzhitsky
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Sergey,
Since we last spoke I had a think about this and a bit of a play and
I've come up with what I reckon is quite an elegant and simple approach
to this, which also "embraces the power of the client side" which
follows the spirit of this GUI :-)
To explain a bit. As I mentioned in my original response the QpidRestAPI
server is intended to be a fairly "thin" layer. Conceptually what I was
trying to achieve was the concept that the *browser* behaves as a proper
QMF Console. What this means is that if you imagine say a python client
like qpid-config creating a Qpid Connection then a Console object and
using that to get QMF Objects that's exactly what I'm getting the
browser to do.
In practice it's not "quite" as simple as that given network
restrictions in the browser, so what actually happens is that when I
create a Qpid Connection in the browser "under the hood" it does a
RESTful PUT to PUT a Qpid Connection resource onto the REST Server (in
other words when a Connection is created in JavaScript that results in a
proxy connection getting created on the QpidRestAPI) once in place that
resource is controlled via RESTful GET/POST and eventually DELETE
methods invoked via jQuery AJAX calls.
That happens independently for any browser connecting, so although the
Connection objects have resource "names" on QpidRestAPI they are best
thought of as "handles" and entirely different to the Connection names
on the GUI, which are intended to be memorable/friendly names for
connections and entirely up to the user. The JavaScript Connection class
actually creates a UUID for the "handle" transparent to the user.
So that's just explaining how the architecture works, but in terms of
simple config - well as it happens in the JavaScript qmfui.Console class
there was a variable called consoleConnections which was used to hold
the array of consoleConnections added in the GUI and this was
initialised to hold the default.
Just to mess around I made this a public property of qmfui.Console e.g.
this.consoleConnections = [{name: "default", url: "",
connectionOptions: ""}];
instead of
var consoleConnections = [{name: "default", url: "",
connectionOptions: ""}];
So why that's significant is it can be used to provide trivially simple
configuration as ultimately it's just a JSON array, so I added the
following line to qmf.html in the ui subdirectory (this has to be after
the line <script src="/qmf-ui/scripts/qmf-ui.js"></script> in the head
block)
<script src="/ui/config.js"></script>
and added the file config.js to the ui subdirectory too (same directory
as the html). In this file I put:
qmfui.Console.consoleConnections = [
{name: "default", url: "", connectionOptions: ""},
{name: "localhost", url: "localhost:5672", connectionOptions: ""},
{name: "wildcard", url: "0.0.0.0:5672", connectionOptions: ""}
];
As you can see it's a fairly straightforward JSON array containing JSON
objects describing the connections you'd like to start out with.
If you don't want anything other than the default just leave config.js
empty.
This is really serving config to the client side, but that's where all
the state is held so it makes a lot more sense than properties on the
server.
The reason I've put the config.js in the ui subdirectory is because that
one is "protected" by the authentication. At the moment I've only got
support for BasicAuthentication so user/passwd are sent clear and be
aware so to would config.js. If you have sensitive usernames/passwords
that's something to be aware of if you want to use this config at the
moment.
For the case of the default URL "" that doesn't get passed to the
browser so you could configure a broker with a user/pass using
./QpidRestAPI -a ...... and that info wouldn't be passed to the browser
because the browser only needs to supply a url of "" to create a
connection using the default connection URL.
It might not be an issue if you're on a private network, but do bear it
in mind. Providing a bit more security is on my "todo" list but it
wasn't top of my priorities initially.
I'll incorporate this stuff into my next release, but as you asked about
this feature I thought that you might be interested - if you're feeling
adventurous you could could tweak your own copy of qmf-ui.js - if you
search for "consoleConnections" in there it's really just a case of
changing "var " to "this." in front of it then adding the tweak to
qmf.html and adding the config.js I describe above.
Let me know how you get on...
Best Regards,
Frase
On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
> Hi Fraser,
>
> Amazing GUI! Thanks a lot!
>
> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>
> config.properties
>
> broker.default=guest/guest@host1:5672
> broker.name2=guest/guest@host2:5672
> broker.name3=guest/guest@host3:5672
>
> broker.default.hide.qmf.objects=true
> broker.name2.hide.qmf.objects=false
> broker.name3.hide.qmf.objects=true
>
> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>
>
> Best Regards,
> Sergey
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Cheers Sergey,
I mentioned the other day I had a hunch it was in that line :-) I was
literally just about to sit down and take a look at it so I'm glad that
I opened my mail when I did.
Thanks for getting there first, I'll can put my feet up now :-)
Couple of comments inline below....
Frase
On 08/02/13 10:48, Zhemzhitsky Sergey wrote:
>
> TypeError: stats.get(...) is undefined
> while ((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
>
>
> I've debugged a little bit and found the following:
>
> 1. msgDepth stats is not a rate stats
>
> var isRate = (description == "msgDepth") ? false : true
Yup that's exactly right, msgDepth is the only statistic being graphed
that isn't a rate - I figured that as things like msgTotalEnqueues etc.
are all absolute monotonically increasing values then it was more useful
to graph the rate.
Unfortunately it's a surprising pain in the butt to do that. When I
started I got some weird results then realised that when I add queues
etc. I was getting statistic updates in rapid succession, which was
(when I thought about it) causing much higher instantaneous rate values.
The while loop where the error is is trying to ensure that the time
delta used is (roughly) 10 seconds.
>
> 2. Next limit=size for a not rate stats
>
> var limit = isRate ? size - 1 : size
>
> 3. Then if we look at
>
> while ((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
>
> the first part of the while loop condition will be executed twice (i=0, i=1) for limit=size=1 and i=0
> so, for i=1 and size=1, stats.get(i) is undefined
>
> What we have to do is to reorder the while loop conditions and everything will be fine, i.e.
>
> while ((i < limit) && (stats.get(i)[TIMESTAMP] < minimumTimestamp)) i++;
>
>
Well spotted! Good old short circuit boolean evaluation, our friend once
again.....
To be honest I'm really surprised that I haven't hit this more often
myself, as I say I almost never see this problem kicking in, so I'd
forgotten about it.
Between you and Bruno Matos you're really piling up my "null pointer"
shame this week :-[
Nice one!
Cheers,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hello Frase,
Thanks a lot for clarification!
>> Hope it's not a show-stopper for you.
Of course it's not a show-stopper.
I've played a little bit with firebug and here is what it's writing on the msgDepth page
TypeError: stats.get(...) is undefined
while ((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
I've debugged a little bit and found the following:
1. msgDepth stats is not a rate stats
var isRate = (description == "msgDepth") ? false : true
2. Next limit=size for a not rate stats
var limit = isRate ? size - 1 : size
3. Then if we look at
while ((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
the first part of the while loop condition will be executed twice (i=0, i=1) for limit=size=1 and i=0
so, for i=1 and size=1, stats.get(i) is undefined
What we have to do is to reorder the while loop conditions and everything will be fine, i.e.
while ((i < limit) && (stats.get(i)[TIMESTAMP] < minimumTimestamp)) i++;
Best Regards,
Sergey
-----Original Message-----
From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
Sent: Wednesday, February 06, 2013 11:58 PM
To: users@qpid.apache.org
Subject: Re: We've got an App for that .... Qpid Web Based GUI - and more - just released.
>>> Is it just msgDepth or do you see the same for msgTotalEnqueues
>>> msgTotalDequeues too
> msgDepth only (event with 1.1 version). All the other pages work pretty fine.
>
>
> Best Regards,
> Sergey
>
>
Thanks for the clarification I've got a hunch about it..... In the graphs page JavaScript there's a line that goes:
while((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
ISTR having intermittent issues with that a while back, though TBH it was *really* infrequent on my set up so I forgot about it. I'd be willing to bet it's that line that's the cause of the problem you're seeing, though given the infrequency for me quite the scenario that causes that condition I'm less sure on, I'll spend a bit of time trying to consistently break it.
I could put a bit more defensive code around it, almost certainly it's
get(...) returning with null, but I'd rather figure out the cause first than just defend against the symptom.
I *hate* bugs like that, it's like it'll take me ten minutes to fix after I've spent two days trying to reproduce it :-) c'est la vie
Hope it's not a show-stopper for you.
Frase.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
>>> Is it just msgDepth or do you see the same for msgTotalEnqueues msgTotalDequeues too
> msgDepth only (event with 1.1 version). All the other pages work pretty fine.
>
>
> Best Regards,
> Sergey
>
>
Thanks for the clarification I've got a hunch about it..... In the
graphs page JavaScript there's a line that goes:
while((stats.get(i)[TIMESTAMP] < minimumTimestamp) && (i < limit)) i++;
ISTR having intermittent issues with that a while back, though TBH it
was *really* infrequent on my set up so I forgot about it. I'd be
willing to bet it's that line that's the cause of the problem you're
seeing, though given the infrequency for me quite the scenario that
causes that condition I'm less sure on, I'll spend a bit of time trying
to consistently break it.
I could put a bit more defensive code around it, almost certainly it's
get(...) returning with null, but I'd rather figure out the cause first
than just defend against the symptom.
I *hate* bugs like that, it's like it'll take me ten minutes to fix
after I've spent two days trying to reproduce it :-) c'est la vie
Hope it's not a show-stopper for you.
Frase.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hello Frase,
>> If you've downloaded version 1.1
I've already tried. It works with Qpid 0.20. Thanks a lot.
>> Is it just msgDepth or do you see the same for msgTotalEnqueues msgTotalDequeues too
msgDepth only (event with 1.1 version). All the other pages work pretty fine.
Best Regards,
Sergey
-----Original Message-----
From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
Sent: Monday, February 04, 2013 10:44 PM
To: users@qpid.apache.org
Subject: Re: We've got an App for that .... Qpid Web Based GUI - and more - just released.
On 04/02/13 12:34, Zhemzhitsky Sergey wrote:
>
> The only issues I've faced with are:
>
> 1. The GUI didn't work with qpid 0.20 client libs (as far as I
> understand it’s already fixed)
If you've downloaded version 1.1 it should work with Qpid 0.20, the issue as you've probably seen on the mailing list related to the way that amqp/list gets exposed to JMS clients. The fix in qmf2-v1.1 used the fact that amqp/list is now exposed as a MapMessage, however after the thread on that subject I was made aware that it's also possible to cast to a Qpid specific ListMessage and get the java.util.list from that. That's much cleaner than messing around with MapMessages so I'll move to that method on the next release.
There are also a bunch on new properties that are available for the queue object in Qpid 0.20 so I'll make sure that they get exposed in a sensible way too.
> 2. After going to queues->queue->msgDepth and clicking here and there
> the GUI controls stops working until page refresh
>
>
Gosh that's one I've not come across, I can't think of a good reason off the top of my head. Is it just msgDepth or do you see the same for msgTotalEnqueues msgTotalDequeues too? do you get the same on the exchange or connection graphs?
The reason I ask is because they actually all navigate to the same graphs page and this gets populated by the same JavaScript class so it's very *interesting* if you are only seeing it on msgDepth and not the others.
Is this something that you are seeing often or is it a bit random/intermittent?
What browser are you using? That said I've tried it on loads :-(
My money is on something like trying to dereference a null object in JavaScript - when you see this are you seeing any JavaScript errors? If you are would you be able to let me know what it's saying. If you are on Chrome or Firefox it'd be *really* great if you'd be able to run something like Web Console to see exactly where it's barfing.
I did *try* to put in a decent amount of defensive coding, but clearly there's no such thing as too much defensive coding.
Anything to narrow it down gratefully received, I'm sure it's something really stupid :-D
Cheers,
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
On 04/02/13 12:34, Zhemzhitsky Sergey wrote:
>
> The only issues I've faced with are:
>
> 1. The GUI didn't work with qpid 0.20 client libs (as far as I understand it’s already fixed)
If you've downloaded version 1.1 it should work with Qpid 0.20, the
issue as you've probably seen on the mailing list related to the way
that amqp/list gets exposed to JMS clients. The fix in qmf2-v1.1 used
the fact that amqp/list is now exposed as a MapMessage, however after
the thread on that subject I was made aware that it's also possible to
cast to a Qpid specific ListMessage and get the java.util.list from
that. That's much cleaner than messing around with MapMessages so I'll
move to that method on the next release.
There are also a bunch on new properties that are available for the
queue object in Qpid 0.20 so I'll make sure that they get exposed in a
sensible way too.
> 2. After going to queues->queue->msgDepth and clicking here and there the GUI controls stops working until page refresh
>
>
Gosh that's one I've not come across, I can't think of a good reason off
the top of my head. Is it just msgDepth or do you see the same for
msgTotalEnqueues msgTotalDequeues too? do you get the same on the
exchange or connection graphs?
The reason I ask is because they actually all navigate to the same
graphs page and this gets populated by the same JavaScript class so it's
very *interesting* if you are only seeing it on msgDepth and not the others.
Is this something that you are seeing often or is it a bit
random/intermittent?
What browser are you using? That said I've tried it on loads :-(
My money is on something like trying to dereference a null object in
JavaScript - when you see this are you seeing any JavaScript errors? If
you are would you be able to let me know what it's saying. If you are on
Chrome or Firefox it'd be *really* great if you'd be able to run
something like Web Console to see exactly where it's barfing.
I did *try* to put in a decent amount of defensive coding, but clearly
there's no such thing as too much defensive coding.
Anything to narrow it down gratefully received, I'm sure it's something
really stupid :-D
Cheers,
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hi Frase,
>> Out of curiosity have you found it pretty responsive
I have > 100 queues and didn't faced with any kind of lags by the time
The only issues I've faced with are:
1. The GUI didn't work with qpid 0.20 client libs (as far as I understand it’s already fixed)
2. After going to queues->queue->msgDepth and clicking here and there the GUI controls stops working until page refresh
Best Regards,
Sergey Zhemzhitsky
Phone. +7 495 2580500 ext. 1246
-----Original Message-----
From: Fraser Adams [mailto:fraser.adams@blueyonder.co.uk]
Sent: Tuesday, January 29, 2013 10:06 PM
To: users@qpid.apache.org
Subject: Re: We've got an App for that .... Qpid Web Based GUI - and more - just released.
There isn't a way to do this as yet, it it's something that I had in the back of my mind.
I'm a little torn, so there's a couple of approaches and they both have merits. At the moment there's a "-a" option to specify a default broker and there's a mechanism to add connections on the GUI.
One slight "complication" is that the way I've designed it is that the GUI behaves very much like a QMF Console connection and the REST API is really just a proxy, so the default is a default URL as opposed to a default connection, the GUI is responsible for asking the REST API to create a connection on its behalf.
So what does that mean. Well specifying a "properties file" is something that is "server side" so it's possible to have the browser "discover" as set of default URLs available so it's something I might look at. However I quite like (and I think favour) the idea of being able to persist the GUI config "client side" so something like HTML5 local storage or even good old cookies.
It's something I'll have a think about - hopefully you can see given the nature of potentially having lots of clients connect to arbitrary brokers via different GUI instances it's not totally trivial to do this in a way that's consistent with some of the design goals that I had for myself.
To be fair one other possibility could make use of security principals, so all the state in the system actually relates to the connection name, but internally I also use the principal to make really sure that these names are unique. That got me thinking that it's be possible to have config on the server side that whilst it may not relate to a specific client instance it does relate to a particular user name.
I still like the idea of storing config on the browser, but there's a few options. I'll have a think :-)
P.S. glad you like the GUI :-) it's really nice that a couple of people
have referred to it as "amazing". An awful lot of work has gone in to it
so it's great that people are starting to play with it and come up with
ideas.
Out of curiosity have you found it pretty responsive? Bruno Matos has
mentioned that he's seen things take a while to update, I'm a bit
baffled by this 'cause that's something I've never come across - I get
updates pretty much regular as clockwork every 10 seconds and if I look
on the brokers page the uptime increases by ~10s every 10s and similarly
if I look at the graphs for the QMF connections they are regularly
updating. What's your experience here?
Cheers,
Frase
On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
> Hi Fraser,
>
> Amazing GUI! Thanks a lot!
>
> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>
> config.properties
>
> broker.default=guest/guest@host1:5672
> broker.name2=guest/guest@host2:5672
> broker.name3=guest/guest@host3:5672
>
> broker.default.hide.qmf.objects=true
> broker.name2.hide.qmf.objects=false
> broker.name3.hide.qmf.objects=true
>
> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>
>
> Best Regards,
> Sergey
>
> ---
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
There isn't a way to do this as yet, it it's something that I had in the
back of my mind.
I'm a little torn, so there's a couple of approaches and they both have
merits. At the moment there's a "-a" option to specify a default broker
and there's a mechanism to add connections on the GUI.
One slight "complication" is that the way I've designed it is that the
GUI behaves very much like a QMF Console connection and the REST API is
really just a proxy, so the default is a default URL as opposed to a
default connection, the GUI is responsible for asking the REST API to
create a connection on its behalf.
So what does that mean. Well specifying a "properties file" is something
that is "server side" so it's possible to have the browser "discover" as
set of default URLs available so it's something I might look at. However
I quite like (and I think favour) the idea of being able to persist the
GUI config "client side" so something like HTML5 local storage or even
good old cookies.
It's something I'll have a think about - hopefully you can see given the
nature of potentially having lots of clients connect to arbitrary
brokers via different GUI instances it's not totally trivial to do this
in a way that's consistent with some of the design goals that I had for
myself.
To be fair one other possibility could make use of security principals,
so all the state in the system actually relates to the connection name,
but internally I also use the principal to make really sure that these
names are unique. That got me thinking that it's be possible to have
config on the server side that whilst it may not relate to a specific
client instance it does relate to a particular user name.
I still like the idea of storing config on the browser, but there's a
few options. I'll have a think :-)
P.S. glad you like the GUI :-) it's really nice that a couple of people
have referred to it as "amazing". An awful lot of work has gone in to it
so it's great that people are starting to play with it and come up with
ideas.
Out of curiosity have you found it pretty responsive? Bruno Matos has
mentioned that he's seen things take a while to update, I'm a bit
baffled by this 'cause that's something I've never come across - I get
updates pretty much regular as clockwork every 10 seconds and if I look
on the brokers page the uptime increases by ~10s every 10s and similarly
if I look at the graphs for the QMF connections they are regularly
updating. What's your experience here?
Cheers,
Frase
On 29/01/13 08:56, Zhemzhitsky Sergey wrote:
> Hi Fraser,
>
> Amazing GUI! Thanks a lot!
>
> I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
>
> config.properties
>
> broker.default=guest/guest@host1:5672
> broker.name2=guest/guest@host2:5672
> broker.name3=guest/guest@host3:5672
>
> broker.default.hide.qmf.objects=true
> broker.name2.hide.qmf.objects=false
> broker.name3.hide.qmf.objects=true
>
> So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
>
>
> Best Regards,
> Sergey
>
> ---
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
RE: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Zhemzhitsky Sergey <Se...@sberbank-cib.ru>.
Hi Fraser,
Amazing GUI! Thanks a lot!
I'm wondering whether there is a possibility to specify all the brokers to connect to in a properties file, i.e.
config.properties
broker.default=guest/guest@host1:5672
broker.name2=guest/guest@host2:5672
broker.name3=guest/guest@host3:5672
broker.default.hide.qmf.objects=true
broker.name2.hide.qmf.objects=false
broker.name3.hide.qmf.objects=true
So all this brokers will be displayed just after restarting of the GUI under the names specified in the properties file.
Best Regards,
Sergey
-----Original Message-----
From: Bruno Matos [mailto:bruno.matos@paradigmaxis.pt]
Sent: Tuesday, January 29, 2013 1:53 AM
To: users@qpid.apache.org
Subject: Re: We've got an App for that .... Qpid Web Based GUI - and more - just released.
Hi Fraser,
On 01/28/2013 09:08 PM, Fraser Adams wrote:
> Hi Bruno,
> Yes that's exactly what I thought was happening too.....
>
> Please do take a look at some of the other posts I've made to the
> mailing list over the last few days.
>
> I made a post entitled "Could somebody *please* explain Java
> Connection URLs" to which Pavel Moravec kindly replied:
>
> "
>
> Hi Fraser,
> there is a bug in Java client disallowing no credentials option,
> seehttps://issues.apache.org/jira/browse/QPID-3396.
>
> Kind regards,
> Pavel
> "
>
> As you may have gathered the "back end" part of the GUI is the
> QpidRestAPI written in Java. You may or may not know this but Java has
> a particular ConnectionURL format documented here:
>
> http://qpid.apache.org/books/0.20/Programming-In-Apache-Qpid/html/Qpid
> JNDI.html#section-jms-connection-url
>
>
> They aren't erm the "most convenient" form to do things with so what I
> did was to write a helper class called "ConnectionHelper" that can
> take URLs in all the main formats - the Java one just gets passed
> through, the one used by the python tools (guest/guest@host:port) and
> the amqp URL used in qpid::messaging should all work and the Class
> basically constructs a Java form Connection URL to pass to JNDI.
>
> Anyways as you've observed if no username/password is supplied this
> defaults to amqp://guest:guest@...... when I saw your last post I
> clocked that and took a closer look.
>
> The spec says
> "amqp://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]"
> so the user/pass *should* be optional, however unfortunately it's not.
>
> I actually started writing that bit an age back ~18 months and I got
> bitten then and forgot about it until your post. I had another go
> trying different approaches, but if you look at my posting there's
> basically currently no way in Java to specify a user ID on anonymous
> (well no way that I've come across and nobody apart from Pavel replied
> to my post so I'm assuming that there won't be a way until that bug is
> fixed).
>
> So from the perspective of my code I'm not sure that there's much I
> can do unless someone can suggest a Connection URL for connecting as
> anonymous - if they can I'll happily change the code to support that.
>
> All I can suggest for the moment if you want to use --auth yes is to
> add a "guest" user in SASL, or better yet a real username/password -
> TBH if you're not doing that you might as well use --auth no.
>
> I hope that this doesn't seem to be a cop-out, I've genuinely tried to
> come up with something - in between getting it to work on Qpid 0.20
> :-(
>
> One possibility is for me to take a look at the patch mentioned in
> Pavel's response. It might be possible for me to create a Connection
> using the Qpid specific implementation classes rather than
> constructing a Connection URL and using the ConnectionFactory. It's
> not ideal but I suspect that it might work, but then I'll be a bit at
> the beck and call if someone tinkers around with those.
>
>
> As an aside you didn't give me any info on the browser you were using
> etc. I still can't think of any reason why it'd take as long as you've
> been suggesting to get updates to queues/exchanges etc. Have you tried
> the new option I've added to disable QMF Events. That switch basically
> switches that particular connection to use timed polling for updates
> instead of receiving Events and using heartbeats to trigger updates.
> Because the async event approach uses AJAX long-polling which "hogs"
> an HTTP connection if you've got a browser with limited connections
> available disabling QMF Events and using a timer driven poll just
> might be more responsive.
>
I'm using Chrome in a Fedora 18. I have a qpid 0.18 in local machine
with auth=yes (default). I also have 0.14 in my office network and
sometimes it works, sometimes it doesn't.
Sorry, I can only spend some minutes testing, so I'm starting from very
beginning and I'm reporting only one thing at time. It works fine for my
needs, by now, and it's amazing, I'm just trying to help testing.
I'll look at this default connection 'problem' first and let you know my
conclusions (if any :)).
> It was just a hunch really, but if neither approach give updates
> pretty regularly every 10 seconds then I'd point the finger at
> something network related on your end. I've never experience the sort
> of symptoms you described and I'd be most interested to hear from
> others. I'm afraid that I can't think what it could be other than I've
> posted here.
>
> Regards,
> Frase
>
>> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
_______________________________________________________
CONFIDENTIALITY NOTICE: This email and any files attached to it may be confidential. If you are not the intended recipient you are notified that using, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify the sender and delete this email.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
Hi Fraser,
On 01/28/2013 09:08 PM, Fraser Adams wrote:
> Hi Bruno,
> Yes that's exactly what I thought was happening too.....
>
> Please do take a look at some of the other posts I've made to the
> mailing list over the last few days.
>
> I made a post entitled "Could somebody *please* explain Java
> Connection URLs" to which Pavel Moravec kindly replied:
>
> "
>
> Hi Fraser,
> there is a bug in Java client disallowing no credentials option,
> seehttps://issues.apache.org/jira/browse/QPID-3396.
>
> Kind regards,
> Pavel
> "
>
> As you may have gathered the "back end" part of the GUI is the
> QpidRestAPI written in Java. You may or may not know this but Java has
> a particular ConnectionURL format documented here:
>
> http://qpid.apache.org/books/0.20/Programming-In-Apache-Qpid/html/QpidJNDI.html#section-jms-connection-url
>
>
> They aren't erm the "most convenient" form to do things with so what I
> did was to write a helper class called "ConnectionHelper" that can
> take URLs in all the main formats - the Java one just gets passed
> through, the one used by the python tools (guest/guest@host:port) and
> the amqp URL used in qpid::messaging should all work and the Class
> basically constructs a Java form Connection URL to pass to JNDI.
>
> Anyways as you've observed if no username/password is supplied this
> defaults to amqp://guest:guest@...... when I saw your last post I
> clocked that and took a closer look.
>
> The spec says
> "amqp://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]"
> so the user/pass *should* be optional, however unfortunately it's not.
>
> I actually started writing that bit an age back ~18 months and I got
> bitten then and forgot about it until your post. I had another go
> trying different approaches, but if you look at my posting there's
> basically currently no way in Java to specify a user ID on anonymous
> (well no way that I've come across and nobody apart from Pavel replied
> to my post so I'm assuming that there won't be a way until that bug is
> fixed).
>
> So from the perspective of my code I'm not sure that there's much I
> can do unless someone can suggest a Connection URL for connecting as
> anonymous - if they can I'll happily change the code to support that.
>
> All I can suggest for the moment if you want to use --auth yes is to
> add a "guest" user in SASL, or better yet a real username/password -
> TBH if you're not doing that you might as well use --auth no.
>
> I hope that this doesn't seem to be a cop-out, I've genuinely tried to
> come up with something - in between getting it to work on Qpid 0.20 :-(
>
> One possibility is for me to take a look at the patch mentioned in
> Pavel's response. It might be possible for me to create a Connection
> using the Qpid specific implementation classes rather than
> constructing a Connection URL and using the ConnectionFactory. It's
> not ideal but I suspect that it might work, but then I'll be a bit at
> the beck and call if someone tinkers around with those.
>
>
> As an aside you didn't give me any info on the browser you were using
> etc. I still can't think of any reason why it'd take as long as you've
> been suggesting to get updates to queues/exchanges etc. Have you tried
> the new option I've added to disable QMF Events. That switch basically
> switches that particular connection to use timed polling for updates
> instead of receiving Events and using heartbeats to trigger updates.
> Because the async event approach uses AJAX long-polling which "hogs"
> an HTTP connection if you've got a browser with limited connections
> available disabling QMF Events and using a timer driven poll just
> might be more responsive.
>
I'm using Chrome in a Fedora 18. I have a qpid 0.18 in local machine
with auth=yes (default). I also have 0.14 in my office network and
sometimes it works, sometimes it doesn't.
Sorry, I can only spend some minutes testing, so I'm starting from very
beginning and I'm reporting only one thing at time. It works fine for my
needs, by now, and it's amazing, I'm just trying to help testing.
I'll look at this default connection 'problem' first and let you know my
conclusions (if any :)).
> It was just a hunch really, but if neither approach give updates
> pretty regularly every 10 seconds then I'd point the finger at
> something network related on your end. I've never experience the sort
> of symptoms you described and I'd be most interested to hear from
> others. I'm afraid that I can't think what it could be other than I've
> posted here.
>
> Regards,
> Frase
>
>> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Bruno,
Yes that's exactly what I thought was happening too.....
Please do take a look at some of the other posts I've made to the
mailing list over the last few days.
I made a post entitled "Could somebody *please* explain Java Connection
URLs" to which Pavel Moravec kindly replied:
"
Hi Fraser,
there is a bug in Java client disallowing no credentials option, seehttps://issues.apache.org/jira/browse/QPID-3396.
Kind regards,
Pavel
"
As you may have gathered the "back end" part of the GUI is the
QpidRestAPI written in Java. You may or may not know this but Java has a
particular ConnectionURL format documented here:
http://qpid.apache.org/books/0.20/Programming-In-Apache-Qpid/html/QpidJNDI.html#section-jms-connection-url
They aren't erm the "most convenient" form to do things with so what I
did was to write a helper class called "ConnectionHelper" that can take
URLs in all the main formats - the Java one just gets passed through,
the one used by the python tools (guest/guest@host:port) and the amqp
URL used in qpid::messaging should all work and the Class basically
constructs a Java form Connection URL to pass to JNDI.
Anyways as you've observed if no username/password is supplied this
defaults to amqp://guest:guest@...... when I saw your last post I
clocked that and took a closer look.
The spec says
"amqp://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]"
so the user/pass *should* be optional, however unfortunately it's not.
I actually started writing that bit an age back ~18 months and I got
bitten then and forgot about it until your post. I had another go trying
different approaches, but if you look at my posting there's basically
currently no way in Java to specify a user ID on anonymous (well no way
that I've come across and nobody apart from Pavel replied to my post so
I'm assuming that there won't be a way until that bug is fixed).
So from the perspective of my code I'm not sure that there's much I can
do unless someone can suggest a Connection URL for connecting as
anonymous - if they can I'll happily change the code to support that.
All I can suggest for the moment if you want to use --auth yes is to add
a "guest" user in SASL, or better yet a real username/password - TBH if
you're not doing that you might as well use --auth no.
I hope that this doesn't seem to be a cop-out, I've genuinely tried to
come up with something - in between getting it to work on Qpid 0.20 :-(
One possibility is for me to take a look at the patch mentioned in
Pavel's response. It might be possible for me to create a Connection
using the Qpid specific implementation classes rather than constructing
a Connection URL and using the ConnectionFactory. It's not ideal but I
suspect that it might work, but then I'll be a bit at the beck and call
if someone tinkers around with those.
As an aside you didn't give me any info on the browser you were using
etc. I still can't think of any reason why it'd take as long as you've
been suggesting to get updates to queues/exchanges etc. Have you tried
the new option I've added to disable QMF Events. That switch basically
switches that particular connection to use timed polling for updates
instead of receiving Events and using heartbeats to trigger updates.
Because the async event approach uses AJAX long-polling which "hogs" an
HTTP connection if you've got a browser with limited connections
available disabling QMF Events and using a timer driven poll just might
be more responsive.
It was just a hunch really, but if neither approach give updates pretty
regularly every 10 seconds then I'd point the finger at something
network related on your end. I've never experience the sort of symptoms
you described and I'd be most interested to hear from others. I'm afraid
that I can't think what it could be other than I've posted here.
Regards,
Frase
> 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
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.
Hope this is useful,
Best regards,
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
On 23/01/13 10:41, Bruno Matos wrote:
> Hi Fraser,
>
> I have configured logs, and I will point some 'issues' that I found.
>
> Sometimes I can see events, but not queues or exchanges. After waiting
> for a while (sometimes I let it run an came back 1 ou 2 minutes later)
> and it's all populated.
That's very strange. In implementation terms how things get updated is
that there's an AJAX connection to the REST API that does the equivalent
of "getWorkItems()" in the QMF API. That's a "long polling" connection
in AJAX speak, so basically it does an HTTP Connection and blocks until
QMF Events (heartbeat, queueDeclare, bind, whatever occur) when one of
these things happens that request returns with the QMF Event response,
that triggers a callback which fires off AJAX requests for the various
management objects. Each request (for queue, exchange, binding etc.) is
a separate AJAX request and I use a jQuery "when()...then()" to trigger
a callback to update the pages when all of the requests have returned.
The AJAX stuff has been around in my code for ages and I'm afraid that
I've never come across anything like you're describing :-( I've tried it
on IE6-IE9, FF 17.0.1, Opera 9 - 12, Chrome (can't recall the version)
and Safari on iOS on an iPad 2 and iPod touch 5, also I've tried on an
Android phone VM and Tablet VM and I've tinkered on a BlackBerry
PlayBook (though not in anger just to see if it looks like it's working OK)
What browser are you running it on? The only thing that I can think of
that might cause this behaviour is if the browser has been set so it
only supports a minimal number of connections to a server. As I say the
Asynchronous Event delivery is done via AJAX long polling, which
essentially keeps hold of a connection so if you have a browser with
only two connections allowed that could cause something like this. That
said like I say I've not seen anything like you describe.
The closest I've seen is in iOS6. That has overly aggressive caching
(there's apparently a bug report in with Apple about it) I had issues
with updating the image on the button "active" state on iOS because it
was trying to do an HTTP GET for the image down the same connection
being used for the long polling. I resolved that by using image sprites
and better image caching, but I've never seen it for the actual data
responses :-/
Some more details on browser etc. might help and if you can figure out
any info on the number of connections it supports (if you're able to try
a different browser and see how that affects what you are seeing that
would be really useful too).
would you be able to describe your setup, maybe that'll give me some
clues. You definitely haven't changed "--mgmt-pub-interval" to anything
other than the 10s default have you? Though if you are seeing events you
should get updates quickly each event that you see will have triggered
the AJAX getObjects() equivalent. So I'm still suspecting something odd
with browser connections and perhaps some network issues you end?
You've only got a single tab with the UI open haven't you? IIRC most
browsers only support a handful of connections to a given domain (which
is where my train of thought is headed) but I *think* different tabs
would each use some of these, so if you happened to open a few tabs to
point to the server that might cause quirky behaviour. I'm suspecting
you haven't done this, but I've got to ask :-)
That said I've just opened six tabs in Firefox with no problems, when I
opened a seventh it took a little longer for the page to load, but all
of the pages look like they are updating with no issues.
I'm afraid I'm a bit baffled on this one, so any more info would be useful.
> I'm running Qpid broker 0.18, with authentication=yes (default) and
> QpidRestAPI, in a FC18.
> In logs, I see
>
> INFO org.apache.qpid.client.AMQConnection - Not a hard-error connection
> not closing: org.apache.qpid.AMQException: ch=1 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]
>
> Browser shows RestAPI disconnected.
So have you tried doing:
./QpidRestAPI -a <user>/<passwd>@<broker-host>:<port>
i.e. giving it a connectionURL to the broker that you want to use as the
default?
If you just do
./QpidRestAPI
with no options the default connection url will be
<host-QpidRestAPI-is-on>:5672 and if you have qpidd --auth yes that
default one won't authenticate (I think).
I think that you mentioned that if you explicitly add a new QMF Console
Connection with the connection URL then you can establish a connection
so I'd be really interested to know what happens if you take the URL
that you add on the setting page and use that in ./QpidRestAPI -a
If you don't specify anything in the -a the code does:
broker = (broker == null) ?
inetaddr.getAddress().getHostAddress() + ":5672" : broker;
Hmm. I'm wondering; "behind the scenes" I end up having to create a Java
ConnectionURL object they end up looking like:
amqp://[<user>:<pass>@][<clientid>]<virtualhost>[?<option>='<value>'[&<option>='<value>']]
Looking at the ConnectionHelper class that I put together to create Java
ConnectionURLs from various different ConnectionURL formats it looks
like that's defaulting the user:pass to guest:guest.
TBH I've only really messed around on brokers with --auth no and that's
happy with the guest:guest
As I say above if you configure the -a option with proper credentials it
*ought* to work. If you get issues it might be worth trying a full Java
Connection URL in the -a option, I'm *pretty sure* that this should be
supported.
>>
> Is the code in the Qpid SVN, or will it be? Should I create JIRAs if I
> think I found a problem?
>
> Thank you.
>
No I'm afraid not, I'm not actually a qpid developer per se I'm really
just a Qpid user trying to give something back to the community. I'm
hoping that it will ultimately make its way into an official Qpid
release. It was actually submitted to the community via the Jira where
you'd have downloaded it from. I don't know what the real process is,
but at this stage the most useful thing to do might be to collate a list
of issues that you've seen and add them as comments to that Jira.
I'll try to have a think about these things ASAP, unfortunately I'm now
back doing "the day job" (I took a few weeks off over Xmas to try and
finally get the GUI released) so I've only really got weekends, but I'll
do what I can within the limits of "family pressure".
HTH,
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
Hi Fraser,
I have configured logs, and I will point some 'issues' that I found.
On Tue, 2013-01-22 at 19:15 +0000, Fraser Adams wrote:
> Hi Bruno/Gordon,
> Thanks for the initial feedback. Gordon it's slightly worrying your
> comment "The problem seems to stem from using the qpid jars from trunk
> (or indeed it seems from 0.20 rc4)". Unfortunately to date I've only had
> a chance to run it against qpidd 0.12 because as I've mentioned
> previously I always had a bit of a fight getting qpidd to make on
> Ubuntu. Now that I've finally got the GUI out there I'll upgrade and see
> if there's any desnagging. There really should be no issues unless
> someone has messed with how qpidd sends QMF messages. The biggest change
> I was aware of was between 0.8 and 0.10 when QMF Events went from Map
> Messages to List Messages, indeed there's actually a bit of your code in
> the QMF2 implementation that does the ampq List Message deserialisation.
> If someone has messed with any of that there could be some issues (I'll
> also be a bit cross because it's not something that was communicated :-))
>
> Re "The default broker has an empty URL" actually that is deliberate,
> but perhaps there needs to be a way to make things more obvious. So what
> happens is that on the REST side you can configure a "default" broker -
> by default that will be a broker running on the same host as the REST
> Server on port 5672. So when the web page loads its initial port of
> call is to create a connection to the default broker (you can add
> connections to different brokers too as you've probably seen). So
> because it's a default that's actually controlled by the REST Server the
> GUI specifies a connection URL of "" initially to mean connect me to the
> default broker.
>
> When you add a new QMF Console Connection you can specifiy whatever
> connection URL you want and the idea is you can give it a memorable name.
>
> Hope that makes sense?
>
> You mention "I also seem to be unable to edit anything or add a qmf
> connection, the text boxes for URL, connection options etc aren't
> editable" That's odd. What browser are you using? The grey bit that says
> guest/guest@host:10000 is just an HTML5 placeholder in a basic input
> type="text" for modern browsers it uses genuine HTML5 placeholders but
> for older ones I wrote a shim, but I've tested it on IE6-9 and Opera 9 -
> 12 and I've never has any problems. Stupid question, you did click on
> the box and try typing didn't you? In all the cases I've tried the
> placeholder disappears as intended and the text you want gets entered?
> Do let me know if it's anything more than finger trouble and if so what
> browser as I say I've tried to try this stuff out across as many
> browsers as I can lay my hands on and I've never experienced the text
> inputs not being editable.
>
> Bruno's comment "the text boxes had the default values, and they only
> disappear after start writing and not on focus, but it worked fine."
> that's exactly it. Actually this might depend on the browser, with the
> recent Firefox I'm using the placeholders disappear only after starting
> typing, with a previous version they disappeared on focus on iOS6 they
> only disappear after starting to type. Placeholders are quite a common
> UI pattern now, sorry if they caused confusion. I had a bit of a design
> goal that the app would look like a "native app" if you ran it on
> something like an iPhone so (as is probably obvious) most of the styling
> attempts to emulate the look and feel of that sort of app.
>
> BTW there's no difference between the "guest" and "admin" accounts at
> present, my intention is to add a permissions type thing so that not
> everyone can add/delete things, but at present they are both exactly the
> same - sorry should have spelled that out. I can't think of any reason
> why you wouldn't be able to click on the text input and start typing.
>
>
> Bruno you said "Sometimes it take some seconds" when you first log in
> (from my experience anyway) or hit browser refresh it should connect
> pretty quickly. The page might take a little while to load depending on
> your network speed as it's a fairly big app, but once you see the
> settings page if you aren't seeing a red banner saying Broker
> Disconnected then it should be running fine. The stats updates are every
> 10 seconds, they are actually triggered by QMF events, so mostly they
> get updated when the QMF heartbeat happens every 10 seconds but if you
> do something like add a queue or whatever then that will trigger a
> refresh too so if you look on the queues page on one browser and add a
> queue on another the new queue should appear pretty much instantly. Hmm
> as I say it's primarily triggered by QMF hearbeats I guess that if you
> have a broker configured with --mgmt-pub-interval to something other
> than the default the refresh could be affected by that..
Sometimes I can see events, but not queues or exchanges. After waiting
for a while (sometimes I let it run an came back 1 ou 2 minutes later)
and it's all populated.
>
> Bruno you also say "Just make sure that you have the new connection
> selected and see the Broker tab" as I said earlier you shouldn't
> necessarily *have to* add and select a new connection as the GUI tries
> to connect to the default url configured on the QpidRestAPI. If you're
> having to explicitly create a new QMF Console Connection then my guess
> is that you are running QpidRestAPI on a host that doesn't have qpidd
> running and you haven't configured QpidRestAPI with an explicit default
> broker it's worth doing ./QpidRestAPI -h
>
> -a <address>, --broker-addr=<address>
> broker-addr is in the form: [username/password@]
> hostname | ip-address [:<port>] e.g.
> localhost, 10.1.1.7:10000, broker-host:10000,
> guest/guest@localhost,
> guest/guest@broker-host:10000
> default is the host QpidRestAPI runs on & port
> 5672.
>
I'm running Qpid broker 0.18, with authentication=yes (default) and
QpidRestAPI, in a FC18.
In logs, I see
INFO org.apache.qpid.client.AMQConnection - Not a hard-error connection
not closing: org.apache.qpid.AMQException: ch=1 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]
Browser shows RestAPI disconnected.
>
> From the post below Gordon it sounds like you've now got it up and
> running. It's a shame that it didn't "just work" for you as I'd hoped.
> If there's any specific gotchas that you came across feel free to add
> them to the Jira comments. I've tried pretty hard to do a good job with
> things like JavaDoc (do take a look at the docs subdirectory in the
> source tree) and the -h switch on the command line, but I've been
> playing with this for such a long time that things which may be obvious
> to me aren't actually obvious at all.
>
>
> I hope that once you got over the initial snags you've found the pages
> and navigation to be pretty intuitive. I've tried to protect people from
> themselves a bit, so for example all of the QMF related queues and
> exchanges have management functions like add/delete etc. disabled 'cause
> it would be a bad idea to delete a QMF queue :-) Similarly when adding
> bindings I've tried to populate as much information as I can
> automatically so if you add a binding from a queue that queue is filled
> in and you get a dynamically populated radio selector for exchanges,
> similarly when you add a binding from an exchange you will see a radio
> selector with all queues except the QMF ones.
>
>
> Hope you're now in a position to have a good play, I'm hoping that you
> don't come across too many other oddities.
>
> I guess that my main motivation behind all of this this it to help
> "sell" Qpid.
>
> You'll remember my comment the other day about selecting products and
> persuading the "hard of thinking" and also needing to be cognescente of
> the "branding" and "product placement". One issue that I've come across
> several times is that command line management tools are great for
> techies but they aren't very "CEO friendly", so having a slightly
> (possibly over) flashy modern looking UI might be the bit of bling
> needed to get people to realise that Qpid is every bit as professional
> as some expensive commercial offering. I *really* hope that it can help
> to further the Qpid cause :-)
Is the code in the Qpid SVN, or will it be? Should I create JIRAs if I
think I found a problem?
Thank you.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
I'm relieved that you're up and running :-)
I wouldn't say it's stupidity not understanding the placeholders. It's
way harder than I'd anticipated to get something that's truly intuitive.
Clearly I haven't succeeded as well as I'd have liked. It's also worth
pointing out that the grey text is truly a placeholder and not a
"default" it's really a "stylistic"/"look and feel" thing.
I agonised a bit about the styling because with this style the text
input box has the same background colour as the list item containing it.
Without the placeholders that would look "dead" but if you look on say
something like an iPad/iPod settings page for adding a mail account
that's the style I was pretty much aiming for. Placeholders are new to
HTML5 and aren't supported on IE6 - 9 hence the shim to make things
consistent. It seems that browsers with native placeholder support
behave differently - as I said previously on the last version of Firefox
I was running the placeholder disappeared on focus but it now disappears
when text is entered, IIRC my shim placeholders disappear on focus. It
can get quite quirky with Opera 11 I discovered that it supported
placeholders for text input, but not textarea (which is what I use for
the connection options and XML binding entry) imagine my surprise :-) I
was nearly driven insane by quirks across browsers and had to be quite
devious to make sure that thing like the radio buttons and checkboxes
got properly "reskinned" for dynamically constructed lists.
One thing I'm quite pleased with is that when you point it at an
iPhone/iPod touch it automatically morphs itself so that the sidebar
becomes the main menu page. It should hopefully work the same on other
smartphones but I'm lacking devices to test it with. I fired up an
Android 'phone and tablet virtual machine and it looks OK with those but
it's possible that other devices might have issues. I've used CSS media
queries to apply styles based on device dimensions so it shouldn't be
hard to make things work if there are issues with other devices but it's
hard to test that without the device.
RE the issues that you've had with the trunk. I guess it's reassuring
that it works across 0.18 or 0.20 brokers, so that probably suggests
it's not an issue with changes to the ManagementAgent.
One thing has got me a little worried. ISTR back in August Rajith
Attapatu posted something about [JMS] ListMessage support. To be honest
I only skimmed it and put it on my "list of things to look at" because I
was trying to focus on the GUI. If Rajith has made any changes to how
the JMS implementation deals with ListMessages then that's going to mess
my QMF2 stuff up a fair bit. As I mentioned earlier I have code (copied
below) that may be familiar to you....Any changes to that will affect
how QMF Events work and as I mentioned earlier I use notification from
heartbeat events to trigger firing off getObject() updates to the
Management Objects. I really hope this hasn't changed, but it's the
first place I'd look.
I might have mentioned this before - but as you can see from the comment
it's this block of code that started me off down the path of writing the
QMF2 API Implementation and ultimately the GUI - so it's all your fault
really :-)
/**
* JMS QMF returns amqp/list types as a BytesMessage this method
decodes that into a java.util.List
* <p>
* Taken from Gordon Sim's initial JMS QMF Example using the BBDecoder
* <p>
* Trivia: This block of code from Gordon Sim is the seed that
spawned the whole of this Java QMF2 API
* implementation - cheers Gordon.
*
* @param message amqp/list encoded JMS Message
* @return a java.util.List decoded from Message
*/
@SuppressWarnings("unchecked")
public static <T> List<T> getList(final Message message) throws
JMSException
{
if (message == null)
{
throw new MessageFormatException("Attempting to do
AMQPMessage.getList() on null Message");
}
else if (message instanceof BytesMessage)
{
BytesMessage msg = (BytesMessage)message;
//only handles responses up to 2^31-1 bytes long
byte[] data = new byte[(int) msg.getBodyLength()];
msg.readBytes(data);
BBDecoder decoder = new BBDecoder();
decoder.init(ByteBuffer.wrap(data));
return (List<T>)decoder.readList();
}
else
{
return null;
}
}
On 22/01/13 20:28, Gordon Sim wrote:
> On 01/22/2013 07:15 PM, Fraser Adams wrote:
>> From the post below Gordon it sounds like you've now got it up and
>> running. It's a shame that it didn't "just work" for you as I'd hoped.
>> If there's any specific gotchas that you came across feel free to add
>> them to the Jira comments.
>
> Yes, my problem was primarily the version of the qpid jars I was
> using. (Plus some of my own stupidity in not understanding the way the
> text boxes with greyed out text worked).
>
> Interestingly the version of the broker doesn't seem to be the issue.
> I can access either 0.18 or 0.20 brokers with the right jars. I
> haven't yet had the time to chase it down further.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Gordon Sim <gs...@redhat.com>.
On 01/22/2013 07:15 PM, Fraser Adams wrote:
> From the post below Gordon it sounds like you've now got it up and
> running. It's a shame that it didn't "just work" for you as I'd hoped.
> If there's any specific gotchas that you came across feel free to add
> them to the Jira comments.
Yes, my problem was primarily the version of the qpid jars I was using.
(Plus some of my own stupidity in not understanding the way the text
boxes with greyed out text worked).
Interestingly the version of the broker doesn't seem to be the issue. I
can access either 0.18 or 0.20 brokers with the right jars. I haven't
yet had the time to chase it down further.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Fraser Adams <fr...@blueyonder.co.uk>.
Hi Bruno/Gordon,
Thanks for the initial feedback. Gordon it's slightly worrying your
comment "The problem seems to stem from using the qpid jars from trunk
(or indeed it seems from 0.20 rc4)". Unfortunately to date I've only had
a chance to run it against qpidd 0.12 because as I've mentioned
previously I always had a bit of a fight getting qpidd to make on
Ubuntu. Now that I've finally got the GUI out there I'll upgrade and see
if there's any desnagging. There really should be no issues unless
someone has messed with how qpidd sends QMF messages. The biggest change
I was aware of was between 0.8 and 0.10 when QMF Events went from Map
Messages to List Messages, indeed there's actually a bit of your code in
the QMF2 implementation that does the ampq List Message deserialisation.
If someone has messed with any of that there could be some issues (I'll
also be a bit cross because it's not something that was communicated :-))
Re "The default broker has an empty URL" actually that is deliberate,
but perhaps there needs to be a way to make things more obvious. So what
happens is that on the REST side you can configure a "default" broker -
by default that will be a broker running on the same host as the REST
Server on port 5672. So when the web page loads its initial port of
call is to create a connection to the default broker (you can add
connections to different brokers too as you've probably seen). So
because it's a default that's actually controlled by the REST Server the
GUI specifies a connection URL of "" initially to mean connect me to the
default broker.
When you add a new QMF Console Connection you can specifiy whatever
connection URL you want and the idea is you can give it a memorable name.
Hope that makes sense?
You mention "I also seem to be unable to edit anything or add a qmf
connection, the text boxes for URL, connection options etc aren't
editable" That's odd. What browser are you using? The grey bit that says
guest/guest@host:10000 is just an HTML5 placeholder in a basic input
type="text" for modern browsers it uses genuine HTML5 placeholders but
for older ones I wrote a shim, but I've tested it on IE6-9 and Opera 9 -
12 and I've never has any problems. Stupid question, you did click on
the box and try typing didn't you? In all the cases I've tried the
placeholder disappears as intended and the text you want gets entered?
Do let me know if it's anything more than finger trouble and if so what
browser as I say I've tried to try this stuff out across as many
browsers as I can lay my hands on and I've never experienced the text
inputs not being editable.
Bruno's comment "the text boxes had the default values, and they only
disappear after start writing and not on focus, but it worked fine."
that's exactly it. Actually this might depend on the browser, with the
recent Firefox I'm using the placeholders disappear only after starting
typing, with a previous version they disappeared on focus on iOS6 they
only disappear after starting to type. Placeholders are quite a common
UI pattern now, sorry if they caused confusion. I had a bit of a design
goal that the app would look like a "native app" if you ran it on
something like an iPhone so (as is probably obvious) most of the styling
attempts to emulate the look and feel of that sort of app.
BTW there's no difference between the "guest" and "admin" accounts at
present, my intention is to add a permissions type thing so that not
everyone can add/delete things, but at present they are both exactly the
same - sorry should have spelled that out. I can't think of any reason
why you wouldn't be able to click on the text input and start typing.
Bruno you said "Sometimes it take some seconds" when you first log in
(from my experience anyway) or hit browser refresh it should connect
pretty quickly. The page might take a little while to load depending on
your network speed as it's a fairly big app, but once you see the
settings page if you aren't seeing a red banner saying Broker
Disconnected then it should be running fine. The stats updates are every
10 seconds, they are actually triggered by QMF events, so mostly they
get updated when the QMF heartbeat happens every 10 seconds but if you
do something like add a queue or whatever then that will trigger a
refresh too so if you look on the queues page on one browser and add a
queue on another the new queue should appear pretty much instantly. Hmm
as I say it's primarily triggered by QMF hearbeats I guess that if you
have a broker configured with --mgmt-pub-interval to something other
than the default the refresh could be affected by that..
Bruno you also say "Just make sure that you have the new connection
selected and see the Broker tab" as I said earlier you shouldn't
necessarily *have to* add and select a new connection as the GUI tries
to connect to the default url configured on the QpidRestAPI. If you're
having to explicitly create a new QMF Console Connection then my guess
is that you are running QpidRestAPI on a host that doesn't have qpidd
running and you haven't configured QpidRestAPI with an explicit default
broker it's worth doing ./QpidRestAPI -h
-a <address>, --broker-addr=<address>
broker-addr is in the form: [username/password@]
hostname | ip-address [:<port>] e.g.
localhost, 10.1.1.7:10000, broker-host:10000,
guest/guest@localhost,
guest/guest@broker-host:10000
default is the host QpidRestAPI runs on & port
5672.
From the post below Gordon it sounds like you've now got it up and
running. It's a shame that it didn't "just work" for you as I'd hoped.
If there's any specific gotchas that you came across feel free to add
them to the Jira comments. I've tried pretty hard to do a good job with
things like JavaDoc (do take a look at the docs subdirectory in the
source tree) and the -h switch on the command line, but I've been
playing with this for such a long time that things which may be obvious
to me aren't actually obvious at all.
I hope that once you got over the initial snags you've found the pages
and navigation to be pretty intuitive. I've tried to protect people from
themselves a bit, so for example all of the QMF related queues and
exchanges have management functions like add/delete etc. disabled 'cause
it would be a bad idea to delete a QMF queue :-) Similarly when adding
bindings I've tried to populate as much information as I can
automatically so if you add a binding from a queue that queue is filled
in and you get a dynamically populated radio selector for exchanges,
similarly when you add a binding from an exchange you will see a radio
selector with all queues except the QMF ones.
Hope you're now in a position to have a good play, I'm hoping that you
don't come across too many other oddities.
I guess that my main motivation behind all of this this it to help
"sell" Qpid.
You'll remember my comment the other day about selecting products and
persuading the "hard of thinking" and also needing to be cognescente of
the "branding" and "product placement". One issue that I've come across
several times is that command line management tools are great for
techies but they aren't very "CEO friendly", so having a slightly
(possibly over) flashy modern looking UI might be the bit of bling
needed to get people to realise that Qpid is every bit as professional
as some expensive commercial offering. I *really* hope that it can help
to further the Qpid cause :-)
Cheers,
Frase
On 22/01/13 15:52, Gordon Sim wrote:
> On 01/22/2013 03:09 PM, Bruno Matos wrote:
>> On Tue, 2013-01-22 at 15:08 +0000, Gordon Sim wrote:
>>> On 01/22/2013 02:50 PM, Gordon Sim wrote:
>>>> On 01/22/2013 02:37 PM, Bruno Matos wrote:
>>>>> Try to add a new QMF Console Connection in the settings page. It
>>>>> worked
>>>>> for me.
>>>>
>>>> That's what I did try. But I can't edit any of the fields on the
>>>> screen
>>>> that presents. Its as if there is no edit permission.
>>>
>>> Ok, that may have been stupidity on my part first time around. I can
>>> now
>>> add a connection that way... however I can't yet get any stats or
>>> entities to show up...
>>
>> Sometimes it take some seconds... Just make sure that you have the new
>> connection selected and see the Broker tab, it should have the basic
>> information.
>
> The problem seems to stem from using the qpid jars from trunk (or
> indeed it seems from 0.20 rc4). The 0.18 jars work (against either a
> 0.18 qpidd or a 0.20/trunk qpidd).
>
> Fraser, this is indeed a *really* nice tool. Far better than anything
> else we have currently for qpidd! Really nice job!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Gordon Sim <gs...@redhat.com>.
On 01/22/2013 03:09 PM, Bruno Matos wrote:
> On Tue, 2013-01-22 at 15:08 +0000, Gordon Sim wrote:
>> On 01/22/2013 02:50 PM, Gordon Sim wrote:
>>> On 01/22/2013 02:37 PM, Bruno Matos wrote:
>>>> Try to add a new QMF Console Connection in the settings page. It worked
>>>> for me.
>>>
>>> That's what I did try. But I can't edit any of the fields on the screen
>>> that presents. Its as if there is no edit permission.
>>
>> Ok, that may have been stupidity on my part first time around. I can now
>> add a connection that way... however I can't yet get any stats or
>> entities to show up...
>
> Sometimes it take some seconds... Just make sure that you have the new
> connection selected and see the Broker tab, it should have the basic
> information.
The problem seems to stem from using the qpid jars from trunk (or indeed
it seems from 0.20 rc4). The 0.18 jars work (against either a 0.18 qpidd
or a 0.20/trunk qpidd).
Fraser, this is indeed a *really* nice tool. Far better than anything
else we have currently for qpidd! Really nice job!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Tue, 2013-01-22 at 15:08 +0000, Gordon Sim wrote:
> On 01/22/2013 02:50 PM, Gordon Sim wrote:
> > On 01/22/2013 02:37 PM, Bruno Matos wrote:
> >> Try to add a new QMF Console Connection in the settings page. It worked
> >> for me.
> >
> > That's what I did try. But I can't edit any of the fields on the screen
> > that presents. Its as if there is no edit permission.
>
> Ok, that may have been stupidity on my part first time around. I can now
> add a connection that way... however I can't yet get any stats or
> entities to show up...
Sometimes it take some seconds... Just make sure that you have the new
connection selected and see the Broker tab, it should have the basic
information.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Gordon Sim <gs...@redhat.com>.
On 01/22/2013 02:50 PM, Gordon Sim wrote:
> On 01/22/2013 02:37 PM, Bruno Matos wrote:
>> Try to add a new QMF Console Connection in the settings page. It worked
>> for me.
>
> That's what I did try. But I can't edit any of the fields on the screen
> that presents. Its as if there is no edit permission.
Ok, that may have been stupidity on my part first time around. I can now
add a connection that way... however I can't yet get any stats or
entities to show up...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Gordon Sim <gs...@redhat.com>.
On 01/22/2013 02:37 PM, Bruno Matos wrote:
> On Tue, 2013-01-22 at 13:38 +0000, Gordon Sim wrote:
>> On 01/20/2013 04:26 PM, Fraser Adams wrote:
>>> To get up and running all that should be required is the Qpid jars on
>>> the classpath and running ant in the root qmf2 directory.
>>>
>>>
>>> Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
>>> bind to the
>>> wildcard address on the host it's running on and port 8080 though this
>>> stuff is configurable.
>>>
>>> Point a browser at <host>:8080 and you should be in business. By default
>>> it will create a default QMF connection to a broker running on the same
>>> host as the QpidRestAPI on port 5672 but the default broker connection
>>> is configurable too.
>>
>> This didn't seem to happen for me. The default broker has an empty URL
>> and none of the broker stats (name, version, port etc) show up.
>>
>> I also seem to be unable to edit anything or add a qmf connection
>> whether logged on via guest or admin (the text boxes for URL, connection
>> options etc aren't editable).
>>
>> What might I be doing wrong?
>>
>> (It does look extremely useful once I get past this initial config
>> hurdle btw so I already echo the thanks & praise offered by Steve and
>> Bruno!)
>>
>
> Try to add a new QMF Console Connection in the settings page. It worked
> for me.
That's what I did try. But I can't edit any of the fields on the screen
that presents. Its as if there is no edit permission.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Tue, 2013-01-22 at 14:37 +0000, Bruno Matos wrote:
> On Tue, 2013-01-22 at 13:38 +0000, Gordon Sim wrote:
> > On 01/20/2013 04:26 PM, Fraser Adams wrote:
> > > To get up and running all that should be required is the Qpid jars on
> > > the classpath and running ant in the root qmf2 directory.
> > >
> > >
> > > Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
> > > bind to the
> > > wildcard address on the host it's running on and port 8080 though this
> > > stuff is configurable.
> > >
> > > Point a browser at <host>:8080 and you should be in business. By default
> > > it will create a default QMF connection to a broker running on the same
> > > host as the QpidRestAPI on port 5672 but the default broker connection
> > > is configurable too.
> >
> > This didn't seem to happen for me. The default broker has an empty URL
> > and none of the broker stats (name, version, port etc) show up.
> >
> > I also seem to be unable to edit anything or add a qmf connection
> > whether logged on via guest or admin (the text boxes for URL, connection
> > options etc aren't editable).
> >
> > What might I be doing wrong?
> >
> > (It does look extremely useful once I get past this initial config
> > hurdle btw so I already echo the thanks & praise offered by Steve and
> > Bruno!)
> >
>
> Try to add a new QMF Console Connection in the settings page. It worked
> for me.
Sorry, I missed the part where you said that have already tried.
I have created a new connection with the admin login, the text boxes had
the default values, and they only disappear after start writing and not
on focus, but it worked fine.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
On Tue, 2013-01-22 at 13:38 +0000, Gordon Sim wrote:
> On 01/20/2013 04:26 PM, Fraser Adams wrote:
> > To get up and running all that should be required is the Qpid jars on
> > the classpath and running ant in the root qmf2 directory.
> >
> >
> > Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
> > bind to the
> > wildcard address on the host it's running on and port 8080 though this
> > stuff is configurable.
> >
> > Point a browser at <host>:8080 and you should be in business. By default
> > it will create a default QMF connection to a broker running on the same
> > host as the QpidRestAPI on port 5672 but the default broker connection
> > is configurable too.
>
> This didn't seem to happen for me. The default broker has an empty URL
> and none of the broker stats (name, version, port etc) show up.
>
> I also seem to be unable to edit anything or add a qmf connection
> whether logged on via guest or admin (the text boxes for URL, connection
> options etc aren't editable).
>
> What might I be doing wrong?
>
> (It does look extremely useful once I get past this initial config
> hurdle btw so I already echo the thanks & praise offered by Steve and
> Bruno!)
>
Try to add a new QMF Console Connection in the settings page. It worked
for me.
Regards.
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more
- just released.
Posted by Gordon Sim <gs...@redhat.com>.
On 01/20/2013 04:26 PM, Fraser Adams wrote:
> To get up and running all that should be required is the Qpid jars on
> the classpath and running ant in the root qmf2 directory.
>
>
> Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
> bind to the
> wildcard address on the host it's running on and port 8080 though this
> stuff is configurable.
>
> Point a browser at <host>:8080 and you should be in business. By default
> it will create a default QMF connection to a broker running on the same
> host as the QpidRestAPI on port 5672 but the default broker connection
> is configurable too.
This didn't seem to happen for me. The default broker has an empty URL
and none of the broker stats (name, version, port etc) show up.
I also seem to be unable to edit anything or add a qmf connection
whether logged on via guest or admin (the text boxes for URL, connection
options etc aren't editable).
What might I be doing wrong?
(It does look extremely useful once I get past this initial config
hurdle btw so I already echo the thanks & praise offered by Steve and
Bruno!)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Bruno Matos <br...@paradigmaxis.pt>.
Hi Fraser,
I've just installed.
One word: AMAZING!
What a great job!! Thank you... a lot!!
(Sorry Steve for repeating you, but I couldn't find better words).
Regards,
Bruno Matos
On Sun, 2013-01-20 at 22:46 +0000, Steve Huston wrote:
> I don't understand some of what you said ;-) but this looks FANTASTIC!
> I'll be looking at this closer in the coming weeks.
>
> THANK YOU!
>
> On 1/20/13 11:26 AM, "Fraser Adams" <fr...@blueyonder.co.uk> wrote:
>
> >For those of you who follow my postings on the Qpid Mailing List you'll
> >probably be aware that I've been doing quite a lot with QMF2.
> >
> >
> >I've just made a fairly major uplift to the QMF2 code base.
> >
> >https://issues.apache.org/jira/browse/QPID-3675
> >
> >
> >There are a few bug fixes to the core Java QMF2 implementation, the most
> >significant being that the ManagementAgent can return multiple partial
> >responses if there are large numbers of objects, the QMF2 getObjects()
> >call now caters for that.
> >
> >However the most significant uplift is the addition of:
> >1) A QMF2 REST API Implementation.
> >2) A JavaScript QMF2 Implementation that uses the REST API as a back end.
> >3) A fully featured Qpid Management Web GUI that does pretty much
> >anything you'd need to do to
> >monitor and manage one or more brokers (it supports connecting to
> >different brokers).
> >
> >The REST and JavaScript QMF2 implementations are fairly complete, the
> >main thing missing is support for QMF2 Query Subscriptions, which are
> >supported in the Java API but I've not got round to adding them to REST
> >& JavaScript versions.
> >
> >The JavaScript implementation uses AJAX to talk to the REST API, this is
> >mainly because that approach is supported on pretty much every browser.
> >I might look to adding WebSocket support IDC when I've got a bit more
> >familiarity with WebSockets.
> >
> >
> >The Web GUI works on multiple browsers and is even functional on IE6
> >:-), it morphs quite well onto mobile devices and uses GPU accelerated
> >animations to give a fairly "native app" feel on iPad/iPhone.
> >
> >The REST API Server was deliberately designed to have almost no
> >dependencies. It uses the com.sun.net.httpserver.HttpServer embedded Web
> >Server that is part of JDK 6 (at least on Sun and OpenJDK) so just
> >requires the Qpid jars on the classpath. It has been designed to make it
> >fairly easy to add a Servlet implementation, but that's not been done
> >yet as the initial goal was to make it fairly dependency free and
> >embedded.
> >
> >The REST API is very RESTful and uses PUT to add Qpid Connections but
> >there is automatic creation of a "default" resource if one tries to do a
> >GET so for example doing:
> >
> >http://<host>:8080/qpid/connection/default/console/objects/queue
> >
> >will retrieve the latest update of the QMF queues as a JSON string,
> >which will parse into a list of QmfConsoleData objects. The QpidServer
> >class JavaDoc documents the complete REST API but hopefully the example
> >above should give the gist (that's the REST equivalent of
> >getObjects("queue") in case it wasn't obvious).
> >
> >
> >To get up and running all that should be required is the Qpid jars on
> >the classpath and running ant in the root qmf2 directory.
> >
> >
> >Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
> >bind to the
> >wildcard address on the host it's running on and port 8080 though this
> >stuff is configurable.
> >
> >Point a browser at <host>:8080 and you should be in business. By default
> >it will create a default QMF connection to a broker running on the same
> >host as the QpidRestAPI on port 5672 but the default broker connection
> >is configurable too.
> >
> >Once running you can add QMF2 Console Connections to other brokers and
> >connect to them via the Web GUI.
> >
> >The main limitation at the moment is the authentication. It uses basic
> >authentication so username/password are sent clear. I'll look to do
> >something better IDC but I wanted to get it released as it represents
> >around a years worth of work over weekends.
> >
> >the authentication file is in
> >qmf2/bin/qpid-web/authentication/authentication.properties and has the
> >traditional
> >admin=admin
> >guest=guest
> >
> >Obviously you might want to change that :-) it supports dynamic changes
> >to the file.
> >
> >FWIW although the Web GUI doesn't yet have better authentication it
> >should be possible to configure the QpidRestAPI to use a default
> >connection to a secure broker. The broker credentials for the default
> >broker aren't returned to the browser - to use the defaults it just
> >supplies a broker URL of "". Obviously the broker management statistics
> >will still be being sent over an unsecure channel but that may not be an
> >issue in many cases.
> >
> >
> >
> >It's all released under the Apache Licence and the GUI uses a JavaScript
> >UI library that I ended up writing as part of this project (called
> >itablet) which should be reusable in other projects.
> >
> >
> >I hope that this is useful to people, as I say it's taken an awful lot
> >of effort to put together, so I'd *really* appreciate feedback.
> >
> >
> >I should point out that this is QMF2 based and so it can only talk to
> >the C++ broker at the moment, however if people are interested and the
> >feedback is positive I'll look to uplifting the back end to also proxy
> >to the JMX mechanism used by the Java broker. I must admit that I've not
> >got any real familiarity with the Java broker, but it ought to be
> >do-able assuming that the Java broker JMX Management Objects have
> >similar capabilities to the C++ QMF Management Objects.
> >
> >Finally if you point it at a broker less than 0.10 the add/delete
> >queue/exchange/binding features won't work as they require broker object
> >create/delete methods that were added in 0.10.
> >
> >I've attached a couple of screen shots of a few different pages on a few
> >different browsers to pique your interest :-)
> >
> >
> >I really hope that the QMF stuff can make it into the main Qpid release
> >at some point, I did the first Java QMF2 API release over a year ago but
> >I've not had much feedback, hopefully with the addition of a management
> >GUI it'll get a bit of traction?
> >
> >Best Regards,
> >Frase
--
Bruno Matos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: We've got an App for that .... Qpid Web Based GUI - and more -
just released.
Posted by Steve Huston <sh...@riverace.com>.
I don't understand some of what you said ;-) but this looks FANTASTIC!
I'll be looking at this closer in the coming weeks.
THANK YOU!
On 1/20/13 11:26 AM, "Fraser Adams" <fr...@blueyonder.co.uk> wrote:
>For those of you who follow my postings on the Qpid Mailing List you'll
>probably be aware that I've been doing quite a lot with QMF2.
>
>
>I've just made a fairly major uplift to the QMF2 code base.
>
>https://issues.apache.org/jira/browse/QPID-3675
>
>
>There are a few bug fixes to the core Java QMF2 implementation, the most
>significant being that the ManagementAgent can return multiple partial
>responses if there are large numbers of objects, the QMF2 getObjects()
>call now caters for that.
>
>However the most significant uplift is the addition of:
>1) A QMF2 REST API Implementation.
>2) A JavaScript QMF2 Implementation that uses the REST API as a back end.
>3) A fully featured Qpid Management Web GUI that does pretty much
>anything you'd need to do to
>monitor and manage one or more brokers (it supports connecting to
>different brokers).
>
>The REST and JavaScript QMF2 implementations are fairly complete, the
>main thing missing is support for QMF2 Query Subscriptions, which are
>supported in the Java API but I've not got round to adding them to REST
>& JavaScript versions.
>
>The JavaScript implementation uses AJAX to talk to the REST API, this is
>mainly because that approach is supported on pretty much every browser.
>I might look to adding WebSocket support IDC when I've got a bit more
>familiarity with WebSockets.
>
>
>The Web GUI works on multiple browsers and is even functional on IE6
>:-), it morphs quite well onto mobile devices and uses GPU accelerated
>animations to give a fairly "native app" feel on iPad/iPhone.
>
>The REST API Server was deliberately designed to have almost no
>dependencies. It uses the com.sun.net.httpserver.HttpServer embedded Web
>Server that is part of JDK 6 (at least on Sun and OpenJDK) so just
>requires the Qpid jars on the classpath. It has been designed to make it
>fairly easy to add a Servlet implementation, but that's not been done
>yet as the initial goal was to make it fairly dependency free and
>embedded.
>
>The REST API is very RESTful and uses PUT to add Qpid Connections but
>there is automatic creation of a "default" resource if one tries to do a
>GET so for example doing:
>
>http://<host>:8080/qpid/connection/default/console/objects/queue
>
>will retrieve the latest update of the QMF queues as a JSON string,
>which will parse into a list of QmfConsoleData objects. The QpidServer
>class JavaDoc documents the complete REST API but hopefully the example
>above should give the gist (that's the REST equivalent of
>getObjects("queue") in case it wasn't obvious).
>
>
>To get up and running all that should be required is the Qpid jars on
>the classpath and running ant in the root qmf2 directory.
>
>
>Once compiled cd to bin and do ./QpidRestAPI.sh by default it tries to
>bind to the
>wildcard address on the host it's running on and port 8080 though this
>stuff is configurable.
>
>Point a browser at <host>:8080 and you should be in business. By default
>it will create a default QMF connection to a broker running on the same
>host as the QpidRestAPI on port 5672 but the default broker connection
>is configurable too.
>
>Once running you can add QMF2 Console Connections to other brokers and
>connect to them via the Web GUI.
>
>The main limitation at the moment is the authentication. It uses basic
>authentication so username/password are sent clear. I'll look to do
>something better IDC but I wanted to get it released as it represents
>around a years worth of work over weekends.
>
>the authentication file is in
>qmf2/bin/qpid-web/authentication/authentication.properties and has the
>traditional
>admin=admin
>guest=guest
>
>Obviously you might want to change that :-) it supports dynamic changes
>to the file.
>
>FWIW although the Web GUI doesn't yet have better authentication it
>should be possible to configure the QpidRestAPI to use a default
>connection to a secure broker. The broker credentials for the default
>broker aren't returned to the browser - to use the defaults it just
>supplies a broker URL of "". Obviously the broker management statistics
>will still be being sent over an unsecure channel but that may not be an
>issue in many cases.
>
>
>
>It's all released under the Apache Licence and the GUI uses a JavaScript
>UI library that I ended up writing as part of this project (called
>itablet) which should be reusable in other projects.
>
>
>I hope that this is useful to people, as I say it's taken an awful lot
>of effort to put together, so I'd *really* appreciate feedback.
>
>
>I should point out that this is QMF2 based and so it can only talk to
>the C++ broker at the moment, however if people are interested and the
>feedback is positive I'll look to uplifting the back end to also proxy
>to the JMX mechanism used by the Java broker. I must admit that I've not
>got any real familiarity with the Java broker, but it ought to be
>do-able assuming that the Java broker JMX Management Objects have
>similar capabilities to the C++ QMF Management Objects.
>
>Finally if you point it at a broker less than 0.10 the add/delete
>queue/exchange/binding features won't work as they require broker object
>create/delete methods that were added in 0.10.
>
>I've attached a couple of screen shots of a few different pages on a few
>different browsers to pique your interest :-)
>
>
>I really hope that the QMF stuff can make it into the main Qpid release
>at some point, I did the first Java QMF2 API release over a year ago but
>I've not had much feedback, hopefully with the addition of a management
>GUI it'll get a bit of traction?
>
>Best Regards,
>Frase
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org