Hi Rob, will the fix be committed to the 0.32 branch as well?
On Wed, Nov 4, 2015 at 3:11 PM, Rob Godfrey wrote:
> Hi Helen,
>
> glad to hear the patch worked for you, we'll make sure that fix is in the
> upcoming 6.0 release (hopefully the Beta for that will be out by the end of
> this week),
>
Hi Helen,
glad to hear the patch worked for you, we'll make sure that fix is in the
upcoming 6.0 release (hopefully the Beta for that will be out by the end of
this week),
Cheers,
Rob
On 4 November 2015 at 21:57, Helen Kwong wrote:
> Hi Rob,
>
> The patch fixed the issue in our tests. It looks
Hi Rob,
The patch fixed the issue in our tests. It looks like we ran into the
problem because we regularly create and close QueueBrowsers sharing the
same session to our set of queues, and while we constantly consume messages
from most queues with MessageConsumers, there can be a small number of
q
Currently it shows:
qpid-config list QueuePolicy
Objects of type 'QueuePolicy'
nameproperties
===
test2_tempSender{u'qpid.lifetime-policy': u'delete-on-close'}
test2_tempSender* {u'qpid.lifetime-policy':
On 11/04/2015 09:24 PM, Michael Ivanov wrote:
Strange.
I just ran qpid-config QueuePolicy again.
It gives the following error:
qpid-config add QueuePolicy test2_tempSender --argument
qpid.lifetime-policy=delete-on-close
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
Strange.
I just ran qpid-config QueuePolicy again.
It gives the following error:
qpid-config add QueuePolicy test2_tempSender --argument
qpid.lifetime-policy=delete-on-close
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text': 'An
object of type QueuePolicy with key
test2_
On 11/04/2015 08:32 PM, Michael Ivanov wrote:
So when I type "qpid-config add QueuePolicy test2_tempSender . . . ." then
test2_tempSender is actually interpreted as queue name prefix?
Yes
Here's the output from qpid-config:
Queue Name Attributes
==
So when I type "qpid-config add QueuePolicy test2_tempSender . . . ." then
test2_tempSender is actually interpreted as queue name prefix?
Here's the output from qpid-config:
Queue Name Attributes
=
On 11/04/2015 07:31 PM, Michael Ivanov wrote:
Thanks for the fix suggestions!
I have applied your patch to qpidd 0.34 and replaced libqpidbroker.so.2.0.0
on test system. I restarted qpidd and verified that no error messages are
generated for qpid-config add QueuePolicy command (there were errors
Hallo,
I have a question about direct message receive in proton.
I tried to receive messages directly using amqp://~1.2.3.4 url.
It works but it seems that queue names in this case are ignored.
I.e. when I subscribe to amqp://~1.2.3.4/q1 I also get the messages
for amqp://~1.2.3.4/q2, q3 etc.
Is
Thanks for the fix suggestions!
I have applied your patch to qpidd 0.34 and replaced libqpidbroker.so.2.0.0
on test system. I restarted qpidd and verified that no error messages are
generated for qpid-config add QueuePolicy command (there were errors with
original version). Then I repeated my test
Hi Tony - I can't answer your question - sorry, but I hope you don't mind if I
forward this onto the 'users@qpid.apache.org' mailing list. You'll reach a
larger audience of users on that list than the proton list.
Hopefully someone with web sockets experience can weigh in.
-K
- Forwarded
On 11/03/2015 09:40 PM, Michael Ivanov wrote:
Sorry, I just went through qpid-config options, qpidd options and I did not find
how one can configure policy for a queue name pattern. Where can I find this
information?
There is some information in the AMQP_1.0 notes alongside the source[1].
So
13 matches
Mail list logo
