Hi Robbie And Rob,
Thank you so much for details.
I completely understand now, we can't do much. Thanks again.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To un
Greetings,
I tried setting lifetime-policy in qmf request and I do not see any difference.
Then I modified messenger.c (starting from line 1768) and set 'exclusive'
property there on source terminus when creating queue using '#' specifier
as follows:
if (pn_streq(name, "#")) {
pn_data_t *
On 07/31/2018 12:18 PM, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a Qpid Proton-J 0.28.1 release, please
test it and vote accordingly.
The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.1-rc1/
The maven artifacts are staged for now at:
On 07/31/2018 11:00 AM, Robbie Gemmell wrote:
Hi folks,
I have put together a spin for a Qpid Proton-J 0.27.3 release, please
test it and vote accordingly.
The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.3-rc1/
The maven artifacts are staged for now at:
On 31 July 2018 at 17:35, Rob Godfrey wrote:
> On Tue, 31 Jul 2018 at 17:18, akabhishek1
> wrote:
>
>> Hi Rob,
>>
>> Thanks for your reply. I also got same comment from Robbie and Timothy.
>>
>> So, I raised this issue with Microsoft and they accepted this issue and
>> they
>> fixed issues in the
On 31 July 2018 at 17:18, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.28.1 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.1-rc1/
>
> The maven artifacts are st
On 31 July 2018 at 16:00, Robbie Gemmell wrote:
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.27.3 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.3-rc1/
>
> The maven artifacts are st
On Tue, 31 Jul 2018 at 17:18, akabhishek1
wrote:
> Hi Rob,
>
> Thanks for your reply. I also got same comment from Robbie and Timothy.
>
> So, I raised this issue with Microsoft and they accepted this issue and
> they
> fixed issues in their SDK which is “azure-servicebus-1.2.7”.
>
> I have done
Olivier,
Yeap, the Web Management Console needs to be changed for that.
I will look into it.
Kind Regards,
Alex
On 31 July 2018 at 15:10, VERMEULEN Olivier wrote:
> Thanks Alex, I just tested it and it works like a charm.
> One thing though, this attribute is not accessible through the graphica
Hi Rob,
Thanks for your reply. I also got same comment from Robbie and Timothy.
So, I raised this issue with Microsoft and they accepted this issue and they
fixed issues in their SDK which is “azure-servicebus-1.2.7”.
I have done testing with “azure-servicebus-1.2.7” and getting expected
er
Hi folks,
I have put together a spin for a Qpid Proton-J 0.28.1 release, please
test it and vote accordingly.
The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.1-rc1/
The maven artifacts are staged for now at:
https://repository.apache.org/content/repositor
The client's responsibility is to say "I want to send to this destination
and I assert that is a queue". This is what the client does.
It is up to the server side to validate the assertion that the client is
making. The client has no information as to whether the server is lying or
not. The er
Hi Tim,
I have created
Destination dest = session.createQueue("test-resource");
I am expecting message should go in Queue and if "queue" is not available
then throw
exception.
Current Behaviour - If "test-resource" named topic exists instead of a Queue
then message is successfully delivered
Hi folks,
I have put together a spin for a Qpid Proton-J 0.27.3 release, please
test it and vote accordingly.
The files can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.3-rc1/
The maven artifacts are staged for now at:
https://repository.apache.org/content/repositor
Thanks Alex, I just tested it and it works like a charm.
One thing though, this attribute is not accessible through the graphical
interface...
Olivier
-Original Message-
From: Oleksandr Rudyy
Sent: mardi 31 juillet 2018 15:22
To: users@qpid.apache.org
Subject: Re: [Broker-J] Reject ove
Hi Olivier,
By default, Qpid exchanges drop unroutable/rejected messages.
You can set exchange "unroutableMessageBehaviour" to "REJECT" in order
to reject the unroutable/rejected messages:
"unroutableMessageBehaviour" : "REJECT"
Kind Regards,
Alex
On 31 July 2018 at 12:44, VERMEULEN Olivier w
Hello,
Actually I managed to reproduce my first use case where the client does not
receive the exception.
It happens when sending through a topic to a queue with REJECT policy enabled.
The message is indeed rejected when the queue is full but the client does not
receive anything...
Olivier
---
17 matches
Mail list logo