You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by akabhishek1 <ma...@gmail.com> on 2018/07/30 17:00:04 UTC
Re: Message going in topic with the use of
"session.createQueue(name)"
HI Robbie And Tim,
It's quite old topic, but still i want to provide update on this issue.
I raised this issue with Microsoft and they accepted this issue and released
fixes in “azure-servicebus-1.2.7”.
I have done testing with “azure-servicebus-1.2.7” and getting expected
error now. They are using "proton-j-0.22.0" internally. I don't know, what
they have done changes to fix this issue but we are getting expected error.
I want to request you, if possible please take a look on this issue again.
It will be great if we can get same feature in Qpid JMS.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Message going in topic with the use of
"session.createQueue(name)"
Posted by akabhishek1 <ma...@gmail.com>.
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 unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Message going in topic with the use of "session.createQueue(name)"
Posted by Robbie Gemmell <ro...@gmail.com>.
On 31 July 2018 at 17:35, Rob Godfrey <ro...@gmail.com> wrote:
> On Tue, 31 Jul 2018 at 17:18, akabhishek1 <ma...@gmail.com>
> 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 testing with “azure-servicebus-1.2.7” and getting expected
>> error now. They are also using "proton-j-0.22.0" internally. I don't know,
>> what they have done changes to fix this issue.
>>
>> After applying their fixes, i am thinking there should be done form client
>> side. That's why, they fixed the issue. I am sorry to say this, i don't
>> have proton-j knowledge otherwise i could share technical implementation
>> details with you.
>>
>> This is not a blocker for us but this will definitely add value in JMS Qpid
>> Client.
>>
>
> To repeat the point... there is *nothing* more the client can do. The
> client doesn't / can't know about the nature of the address. The client is
> saying "I expect this to be a queue". Proton-J is a generic AMQP client,
> it is designed to work with the AMQP specification rather than a particular
> implementation of it. If ServcieBus is not responding to the client with
> either a failure to attach, or by explicitly saying "this is a topic" then
> how can the client do anything else. From Microsoft's point of view they
> may be able to add logic to their client libraries which depends on the
> behaviour of ServiceBus, but as a generic client Qpid JMS cannot do that.
> Qpid JMS relies on the system it is connecting to to respect AMQP defined
> behaviours.
>
> -- Rob
To add to Rob's message, in this case the change seemingly being
referenced looks to be
https://github.com/Azure/azure-service-bus-java/pull/240/files, in
which a vendor-specific link-property called
"com.microsoft:entity-type" is added and used by the client(+server?)
in order to achieve the functionality, so that isnt something we would
be making use of.
Robbie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Message going in topic with the use of "session.createQueue(name)"
Posted by Rob Godfrey <ro...@gmail.com>.
On Tue, 31 Jul 2018 at 17:18, akabhishek1 <ma...@gmail.com>
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 testing with “azure-servicebus-1.2.7” and getting expected
> error now. They are also using "proton-j-0.22.0" internally. I don't know,
> what they have done changes to fix this issue.
>
> After applying their fixes, i am thinking there should be done form client
> side. That's why, they fixed the issue. I am sorry to say this, i don't
> have proton-j knowledge otherwise i could share technical implementation
> details with you.
>
> This is not a blocker for us but this will definitely add value in JMS Qpid
> Client.
>
To repeat the point... there is *nothing* more the client can do. The
client doesn't / can't know about the nature of the address. The client is
saying "I expect this to be a queue". Proton-J is a generic AMQP client,
it is designed to work with the AMQP specification rather than a particular
implementation of it. If ServcieBus is not responding to the client with
either a failure to attach, or by explicitly saying "this is a topic" then
how can the client do anything else. From Microsoft's point of view they
may be able to add logic to their client libraries which depends on the
behaviour of ServiceBus, but as a generic client Qpid JMS cannot do that.
Qpid JMS relies on the system it is connecting to to respect AMQP defined
behaviours.
-- Rob
> Regards,
> Abhishek Kumar
>
>
>
> --
> Sent from:
> http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Message going in topic with the use of
"session.createQueue(name)"
Posted by akabhishek1 <ma...@gmail.com>.
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
error now. They are also using "proton-j-0.22.0" internally. I don't know,
what they have done changes to fix this issue.
After applying their fixes, i am thinking there should be done form client
side. That's why, they fixed the issue. I am sorry to say this, i don't
have proton-j knowledge otherwise i could share technical implementation
details with you.
This is not a blocker for us but this will definitely add value in JMS Qpid
Client.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Message going in topic with the use of "session.createQueue(name)"
Posted by Rob Godfrey <ro...@gmail.com>.
The client's responsibility is to say "I want to send to this destination
<foo> and I assert that <foo> 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 error you encountered was purely because of the bug on the server
(Azure) side (it was saying "your assertion is correct, <foo> is a queue"),
there is nothing more that the client can do.
-- Rob
On Tue, 31 Jul 2018 at 16:46, akabhishek1 <ma...@gmail.com>
wrote:
> 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 to topic "test-resource" instead of
> throwing exception.
>
> Feature Request - if i create Queue Destination then message should go in
> Queue and if same resource not available as Queue then throw exception.
>
> Please let me know for any concern/question.
>
> Regards,
> Abhishek Kumar
>
>
>
>
> --
> Sent from:
> http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Message going in topic with the use of
"session.createQueue(name)"
Posted by akabhishek1 <ma...@gmail.com>.
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 to topic "test-resource" instead of
throwing exception.
Feature Request - if i create Queue Destination then message should go in
Queue and if same resource not available as Queue then throw exception.
Please let me know for any concern/question.
Regards,
Abhishek Kumar
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Message going in topic with the use of
"session.createQueue(name)"
Posted by Timothy Bish <ta...@gmail.com>.
On 07/30/2018 01:00 PM, akabhishek1 wrote:
> HI Robbie And Tim,
>
> It's quite old topic, but still i want to provide update on this issue.
>
> I raised this issue with Microsoft and they accepted this issue and released
> fixes in “azure-servicebus-1.2.7”.
>
> I have done testing with “azure-servicebus-1.2.7” and getting expected
> error now. They are using "proton-j-0.22.0" internally. I don't know, what
> they have done changes to fix this issue but we are getting expected error.
>
> I want to request you, if possible please take a look on this issue again.
> It will be great if we can get same feature in Qpid JMS.
What feature are you requesting for Qpid JMS? From the previous
discussion on the list on this thread I don't see anything that wasn't
already working as it should in the client.
> Regards,
> Abhishek Kumar
>
>
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org