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 IndexClusteringHow MQ Client works with cluster

Post new topicReply to topic
How MQ Client works with cluster View previous topic :: View next topic
Author Message
Sosed
PostPosted: Tue May 15, 2018 10:26 am Post subject: How MQ Client works with cluster Reply with quote

Apprentice

Joined: 24 Aug 2012
Posts: 43

Hello guys.

I have a question about MQ Client ability to work with clustered queues.

Everybody knows "classic" case: MQ Client connects to a partial repository node (PR1) and writes a message into a cluster queue, which is owned by another pertial repository node (PR2). It is possible because PR1 node gets connection info from one of full repositories and dinamically creates a channel to PR2.



And it works fine even if all FR nodes go down (assuming PR1 has already connected to PR2 at least once):



Here is the question. Is it possible for MQ Client to work the same way as PR1? To dynamically establish a connection to PR2 (without explicit manual configuration, as PR1 in the previous example did)?

For example, MQ Client connects to one of full repositories (FR1) via CCDT. It has no information about other members of the cluster, only connection to FR1 node. Application writes a message via MQ Client into a cluster queue, which is owned by PR2.



Is it possible for MQ Client to communicate with cluster queue if both FR go down?



I didn't find any info supporting this idea.
I also tried to run the case (with rfhutilc and simple Java app (MQ classes for Java) as Clients; I didn't use CCDT, only direct connections) - no success.
So, it's impossible? Or I missed something (like specific options)?

_____________________________________________________________

And a couple of question more:
2. When MQ Client writes into a cluster queue, it works with only one QM (which the client connected to) and the QM redirects messages? Or MQ Client establishes a connection to the target QM?
3. Can MQ Client "cache" cluster topology after connection to one of the cluster members and then use cached info to connect in a random way to any of cluster members without manual configuration like connection list, CCDT?

Thank you in advance!
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue May 15, 2018 11:12 am Post subject: Re: How MQ Client works with cluster Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25244
Location: Ohio, USA

Sosed wrote:

Here is the question. Is it possible for MQ Client to work the same way as PR1? To dynamically establish a connection to PR2 (without explicit manual configuration, as PR1 in the previous example did)?

For example, MQ Client connects to one of full repositories (FR1) via CCDT. It has no information about other members of the cluster, only connection to FR1 node. Application writes a message via MQ Client into a cluster queue, which is owned by PR2.


No. The client has no awareness of clusters, only queue managers. You could achieve the same effect by loading the CCDT with all the PR queue managers in the cluster, though you'd need to add new PRs manually

Sosed wrote:

Is it possible for MQ Client to communicate with cluster queue if both FR go down?


Yes. Because it will probably be connected to a PR which has the location of the queue

Sosed wrote:

2. When MQ Client writes into a cluster queue, it works with only one QM (which the client connected to) and the QM redirects messages? Or MQ Client establishes a connection to the target QM?


Again, the client is connected to a specific queue manager. That queue manager is responsible for all name resolution. A cluster is just a particular type of name resolution, using a separate repository.

Sosed wrote:
3. Can MQ Client "cache" cluster topology after connection to one of the cluster members and then use cached info to connect in a random way to any of cluster members without manual configuration like connection list, CCDT?


No, because the client knows nothing about clusters.
_________________
Honesty is the best policy.
Insanity is the best defence.
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 IndexClusteringHow MQ Client works with cluster
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.