On 02/02/2013 12:02 PM, Fraser Adams wrote:
So I'm thinking that there might have been some changes between Qpid
versions? I've currently got the 0.20 Java jars on my classpath, but my
broker is still 0.12, but Bruno reckons he's been using 0.18 at home and
I think 0.14 at work so my hunch is
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
I hope to make some further progress with AMQP 1.0 support for the next
release. Some of the gaps remaining are:
* inter-broker links
This allows qpidd to be hooked into wider 1.0 based networks which
expands the options for building or evolving systems.
* lifetime policy for nodes created
Hi Gordon,
* support for the assert option
This support includes disable all assertions, including the existence of
the endpoint, as we discussed some time ago?
Thank you,
Regards.
On Seg, 2013-02-04 at 13:53 +, Gordon Sim wrote:
I hope to make some further progress with AMQP 1.0 support
On 02/04/2013 02:59 PM, Bruno Matos wrote:
Hi Gordon,
* support for the assert option
This support includes disable all assertions, including the existence of
the endpoint, as we discussed some time ago?
Good question! Though in 1.0 the situation is somewhat different from
0-10[1], calls to
Hi Gordon,
I hope to make some further progress with AMQP 1.0 support for the next
release. Some of the gaps remaining are:
* inter-broker links
This allows qpidd to be hooked into wider 1.0 based networks which expands
the options for building or evolving systems.
Does this require any
Hi Ken,
It didn't work. The message stays in the B2 and no message is sent for
B1 queue.
Anyway, I was hoping that would be a more transparent way to do this.
Replicating all the queues seams overkill.
One way could be change the default exchange to something else, but that
means change the
Hi Gordon turning out setting to Browse fixed the memory issue. Also one of
the queues did not having a limit on it. Setting a limit resolved the
issue. Thanks
On Fri, Feb 1, 2013 at 6:42 AM, Rajesh Khan rajeshkhan...@gmail.com wrote:
Just looked at the code and to my surprise I am not browsing
This morning when I started my computer Qpidd wouldnt accept and queues.
I usually start my Qpidd boker with the following command:
*qpidd --auth=no *
Now I am attempting to add a queue to it as such
*D:\qpid-0.18\qpid-0.18\tools\src\pypython qpid-config add queue Testing
Just a minor correction - Qpid wouldn't accept any queues
On Mon, Feb 4, 2013 at 9:41 AM, Rajesh Khan rajeshkhan...@gmail.com wrote:
This morning when I started my computer Qpidd wouldnt accept and queues.
I usually start my Qpidd boker with the following command:
*qpidd --auth=no *
Now I am
On 02/04/2013 04:14 PM, Steve Huston wrote:
Hi Gordon,
I hope to make some further progress with AMQP 1.0 support for the next
release. Some of the gaps remaining are:
* inter-broker links
This allows qpidd to be hooked into wider 1.0 based networks which expands
the options for building or
On 02/04/2013 04:26 PM, Rajesh Khan wrote:
Hi Gordon turning out setting to Browse fixed the memory issue. Also one of
the queues did not having a limit on it. Setting a limit resolved the
issue. Thanks
Great, thanks for updating us! I still think you have most likely
uncovered some bug, but
Ok, good. I was concerned because I've heard of a major possible AMQP using
community who elected not to use AMQP because of the lack of broker federation
standardization. I would like this point squashed. Is there a chance you'll be
able to make progress on this area of Qpid sufficiently to
On 02/04/2013 04:25 PM, Bruno Matos wrote:
Anyway, I was hoping that would be a more transparent way to do this.
Replicating all the queues seams overkill.
One way could be change the default exchange to something else, but that
means change the behavior of many components in the system.
That
On 02/04/2013 04:59 PM, Steve Huston wrote:
Ok, good. I was concerned because I've heard of a major possible AMQP using
community who elected not to use AMQP because of the lack of broker federation
standardization. I would like this point squashed.
Yes, I have also heard that being raised.
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
On 02/04/2013 11:59 AM, Steve Huston wrote:
Ok, good. I was concerned because I've heard of a major possible AMQP using
community who elected not to use AMQP because of the lack of broker
federation standardization.
I find that amusing, someone would rather select something entirely
Hello, this is my first time mailing to this group.
The qpid-tool --help page and other references mention that one of the options
for setting queue limit-policy is:
none (default) - Use broker's default policy.
I have searched high and low throughout all the documentation and done much
18 matches
Mail list logo
