ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportAMQP Competing Consumer Scenario

Post new topicReply to topic
AMQP Competing Consumer Scenario View previous topic :: View next topic
Author Message
bbattah
PostPosted: Wed Sep 18, 2019 9:09 am Post subject: AMQP Competing Consumer Scenario Reply with quote

Newbie

Joined: 18 Sep 2019
Posts: 1

I am trying to use AMQP 1.0 connection from C# (via nuget package Microsoft.Azure.Amqp 2.4.3) with IBM MQ 9.0.1 (trial) in order to support a competing consumer pattern previously implemented on RabbitMQ.

I can get pub/sub working for a single consumer using the aforementioned technology stack, but I have two substantial challenges:

1.) I cannot seem to get a durable subscription (confirmed "durable=true" in MQ Explorer GUI) to survive starting and stopping an amqp connection. Even a manually created subscription is deleted after the first consumer closes down. In fact, if I start a consumer and leave it connected with zero link-credits, then submit messages and finally disconnect the consumer - then the subscription and my *unread* messages are lost. I have reviewed the WireShark trace but nothing stands out as "off" with the AMQP traffic. Can anyone suggest what I should be looking to confirm in the traffic to get the created subscription to outlive the AMQP connection which created it?

2.) Furthermore, if I add more than one consumer to a "shared subscription" (example: :share:subName:existingtopic) I am getting an any-cast behavior which seems generally correct but the broker does not behave as I would expect in the case of a failed consumer. I expect it to re-deliver "unsettled" messages to any surviving consumer(s) in the case of a disconnected\failed consumer. Is this a reasonable expectation?

It is nearly certain that I am doing something wrong or have mis-configured something but I really need some advice. Are my expectations wrong? Where should I be looking to break-down the problem into pieces to be analyzed?

Thanks in advance for any guidance!
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportAMQP Competing Consumer Scenario
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.