Thanks a lot for the patch! But it looks like qpid-jms v 0.6.0 works as expected
without policy settings altogether. We were using v 0.30 all the time (and later
tried 0.32) and the queues were left over. But as soon as we switched to 0.6.0
the problem dissappeared.
Just in case similar problem wi
On 11/05/2015 10:28 AM, Michael Ivanov wrote:
Is there a chance to get it working for 0.34 in foreseeable future? :-)
I have committed a fix to trunk (QPID-6834), also attached as another patch.
Also, I have committed support for ANONYMOUS_RELAY, which I think would
provide another workaround
That filename looks like it for the AMQP 0-x JMS client. Gordon and I
were referring to the two AMQP 1.0 JMS clients as you had mentioned
using the earlier of those ('qpid-amqp-1-0-client-jms', in this case
0.30) in a previous mail. The newer AMQP 1.0 JMS client we mentioned
is the 'qpid-jms-client
I just tried qpid-client-0.32-bin.tar.gz (we were using 0.30). Still the same.
Is this version to be considered new or should I search for sthing else?
Best regards,
05.11.2015 15:37, Gordon Sim пишет:
> On 11/05/2015 12:06 PM, Robbie Gemmell wrote:
>> On 5 November 2015 at 11:45, Gordon Sim wro
On 11/05/2015 12:06 PM, Robbie Gemmell wrote:
On 5 November 2015 at 11:45, Gordon Sim wrote:
If there was a way to configure the dynamic-node-properties requested in
this case, then the desired lifetime-policy could be selected. (I had
incorrectly assumed that the 'S' process was also using mes
On 5 November 2015 at 11:45, Gordon Sim wrote:
> On 11/05/2015 10:32 AM, Michael Ivanov wrote:
>>
>> And it's still the question why the policy is not set for the queue
>> created with:
>>
>> responseQueue = session.createTemporaryQueue();
>>
>> when using qpid-amqp-1-0-client-jms-0.30.jar
On 11/05/2015 10:32 AM, Michael Ivanov wrote:
And it's still the question why the policy is not set for the queue created
with:
responseQueue = session.createTemporaryQueue();
when using qpid-amqp-1-0-client-jms-0.30.jar package?
That will most likely involve a receiving link with a d
And it's still the question why the policy is not set for the queue created
with:
responseQueue = session.createTemporaryQueue();
when using qpid-amqp-1-0-client-jms-0.30.jar package?
If I delete the queue created from java manually and then use the same queue
name
with recv test utility
Is there a chance to get it working for 0.34 in foreseeable future? :-)
05.11.2015 13:27, Gordon Sim пишет:
> On 11/05/2015 10:14 AM, Michael Ivanov wrote:
>> Ok it worked! Probably last time when running recv I mistyped the queue name.
>> But weherever I run recv with such name queue is created a
On 11/05/2015 10:14 AM, Michael Ivanov wrote:
Ok it worked! Probably last time when running recv I mistyped the queue name.
But weherever I run recv with such name queue is created and when the recv
stopped
the queue was automatically deleted. But! It is also deleted when the send
utility
termi
Ok it worked! Probably last time when running recv I mistyped the queue name.
But weherever I run recv with such name queue is created and when the recv
stopped
the queue was automatically deleted. But! It is also deleted when the send
utility
terminated! So the receiver gets only one message. Al
On 11/05/2015 09:38 AM, Michael Ivanov wrote:
Do you mean recv example utility from proton?
Yes
I tried it but it does not create the receive queue automatically
So if you run (with localhost replaced by the actual hostname if
necessary, and the exact details of the uuid part not important
Do you mean recv example utility from proton?
I tried it but it does not create the receive queue automatically
Should I create one manually?
I tried (qpid-config add queue test2_tempSender12345) and qpid-config queues
output is still without delete-on-close policy.
05.11.2015 12:21, Gordon Sim пи
On 11/04/2015 09:37 PM, Michael Ivanov wrote:
Currently it shows:
qpid-config list QueuePolicy
Objects of type 'QueuePolicy'
nameproperties
===
test2_tempSender{u'qpid.lifetime-policy': u'delete-on-close
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
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
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
03.11.2015 23:51, Gordon Sim пишет:
> On 11/03/2015 08:25 PM, Michael Ivanov wrote:
>> I use c++ qpid broker 0.34 and proton library v 0.10. I am using 2 processes:
>> receiver process (R) which reads the messages and sends replies when
>> requested
>> and sender (S) process which creates temporar
On 11/03/2015 08:25 PM, Michael Ivanov wrote:
I use c++ qpid broker 0.34 and proton library v 0.10. I am using 2 processes:
receiver process (R) which reads the messages and sends replies when requested
and sender (S) process which creates temporary queues, sends messages to R and
requests a repl
Hallo Gordon, thanks for the response,
I use c++ qpid broker 0.34 and proton library v 0.10. I am using 2 processes:
receiver process (R) which reads the messages and sends replies when requested
and sender (S) process which creates temporary queues, sends messages to R and
requests a reply. Proce
On 11/03/2015 05:57 PM, Michael Ivanov wrote:
Hallo,
Please help me to resolve the following situation:
I create a temporary queue using "/#" suffix to amqp url. The queue is created
with name like 36275A5C-8630-457B-BD75-3664354ECC2D_#
I set this queue as reply_to address in messages being se
Hallo,
Please help me to resolve the following situation:
I create a temporary queue using "/#" suffix to amqp url. The queue is created
with name like 36275A5C-8630-457B-BD75-3664354ECC2D_#
I set this queue as reply_to address in messages being sent. I receive the reply
message and run pn_messe
27 matches
Mail list logo
