Hi Connor,
this is not possible either C++ broker version. Default limit policy reject
is hardcoded.
Note that since qpid 0.20 there are only two limit policies, reject and ring,
until a replacement of flow-to-disk is implemented
(https://issues.apache.org/jira/browse/QPID-4339).
Kind
Hi Gordon,
Another good question!
In establishing a link to another broker, qpidd is not doing anything
that other client libraries must be able to do. From the perspective of
that other broker qpidd can be treated as just another producer or consumer.
However there are aspects that
Hi Gordon,
On Seg, 2013-02-04 at 16:11 +, Gordon Sim wrote:
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
Hi Fraser,
I've started a new thread to clean history, I hope you don't mind.
In the login window, if I use a wrong password it resets all text boxes
(as expected), but if I use a wrong username the browser (chrome) shows
an error page and I have to restart the browser to see the login window
On 02/05/2013 10:26 AM, Bruno Matos wrote:
Hi Gordon,
Another good question!
In establishing a link to another broker, qpidd is not doing anything
that other client libraries must be able to do. From the perspective of
that other broker qpidd can be treated as just another producer or
On 02/05/2013 10:46 AM, Bruno Matos wrote:
Hi Gordon,
On Seg, 2013-02-04 at 16:11 +, Gordon Sim wrote:
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
On 02/05/2013 01:36 AM, Paul O'Fallon wrote:
Hello. I wanted to follow up and mention that I tried this again by
building qpid from the trunk (via cmake) and I still get the same error
(Unsupported protocol). Is there something else I need to do beyond
installing proton (which it says it
On 05/02/13 11:28, Bruno Matos wrote:
Hi Fraser,
I've started a new thread to clean history, I hope you don't mind.
No not at all that makes sense. That's actually quite amusingly
appropriate given the nature of the new thread :-D
In the login window, if I use a wrong password it resets all
Hi,
sorry I didn't get back on this.
Given the behaviour that you're suggesting I'm wondering whether you
care about acks at all? With the C++ qpid::messaging API and JMS it's
possible to configure an Address String with link: {reliability:
unreliable} which says that the consumer application
On 02/05/2013 06:42 PM, Gordon Sim wrote:
On 02/05/2013 01:36 AM, Paul O'Fallon wrote:
Hello. I wanted to follow up and mention that I tried this again by
building qpid from the trunk (via cmake) and I still get the same error
(Unsupported protocol). Is there something else I need to do
Thanks for sharing all the options.
I actually want to go with the approach of deleting the queue itself from
the broker when connection is getting lost. Any way I am creating separate
queue for each Sender and receiver point to point communication(I hope it
will not impact any thing in the
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
12 matches
Mail list logo
