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
12 matches
Mail list logo
