|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Problems while configuring cluster |
« View previous topic :: View next topic » |
Author |
Message
|
Sach |
Posted: Tue Jun 11, 2013 6:44 pm Post subject: Problems while configuring cluster |
|
|
Newbie
Joined: 11 Jun 2013 Posts: 5
|
Hi,
I am new to WebSphere MQ and Iam following IBM document for creating cluster.
The configuration I did was
2 QMGR namely LONDON and NEWYORK on two different machines.
I created CLUSRCVR and CLUSRCVR channels on both QMGR's and created Queue INVENTQ with the following command.
DEFINE QLOCAL(INVENTQ) CLUSTER(INVENTORY)
Initially I was not able to send any messages from QMGR London to Newyork as all the messages were getting stored locally. I changed the qmgr attribute settings to clwluseq(any) after which i am able to get messages on both the cluster.
The problem is, if i send 5 messages on London, 2 messages are on the local queue and i could see 3 messages on Newyork. I am not able to access all messages put in Inventq on either of the cluster members. Is this is normal behavior, if not how could i rectify this problem.
For testing purposes i created two queues like Inventq.LDN on qmgr LONDON and Inventq.NYW on qmgr NEWYORK and i was able to send message from either of the clusters and receive on the QMGR where these queues are defined i.e. i could receive messages sent to Inventq.LDN from both machines on LONDON and messages sent to Inventq.NYW from both machines on NEWYORK. I need the same behavior for Inventq queue.
Regards,
Sach |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Jun 11, 2013 9:23 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
What do you mean by 'Im not able to access all the messages?'
What application are you using? Where are you using it? What symptom do you see? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
McueMart |
Posted: Wed Jun 12, 2013 1:14 am Post subject: |
|
|
 Chevalier
Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere
|
With MQ you can PUTs to remote destinations, but can only GET locally. Therefore when you are workload balancing around your cluster, your PUTs will go to each cluster member which has an instance of the queue, but when you are GETing, you will only be able to access messages on the QM you are connected to.
This is expected behavior. I think this is what you are asking but I might be wrong. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jun 12, 2013 2:27 am Post subject: Re: Problems while configuring cluster |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Sach wrote: |
I changed the qmgr attribute settings to clwluseq(any) after which i am able to get messages on both the cluster. |
There are several other places you could have changed other things to achieve the same result.
The best thing to change would be the application-level bind option to BIND_NOT_FIXED on the MQOPEN. |
|
Back to top |
|
 |
Sach |
Posted: Thu Jun 13, 2013 8:00 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2013 Posts: 5
|
The problem i am facing is i am putting 15 messages into the queue INVENTQ on LONDON QMGR which is part of the cluster, When i check the messages available on NEWYORK QMGR i see that the messages 1,3,5,7,9,11,13 and 15 being available and when i check on LONDON QMGR i see the messages 2,4,6,8,10,12 and 14. I wanted to know if this is the expected behavior and is there any way by which all messages sent into INVENTQ from LONDON QMGR be available on NEWYORK QMGR because as per this scenario say if there are 5 members in a cluster then each member will receive only 3 messages hence the application accessing the cluster member will not be having whole message but a part of the message. Please correct me if i am wrong somewhere as i am new to MQ and still learning.
I tried using the DEFBIND(NOTFIXED) as well, but still the results are same. To better understand my question i have attached the screenshot at https://skydrive.live.com/redir?resid=62F7ECE3425548D8!969&authkey=!ABCHJLn2xeJINpM |
|
Back to top |
|
 |
Sach |
Posted: Thu Jun 13, 2013 8:02 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2013 Posts: 5
|
The correct URL of the image is "https://skydrive.live.com/?cid=62f7ece3425548d8&id=62F7ECE3425548D8%21969&sff=1&authkey=!ABCHJLn2xeJINpM".
The reason why i am asking whether the behavior is correct or because as per the sample setup provided by IBM, it is mentioned that messages sent on LONDON QMGR will be available on NEWYORK QMGR |
|
Back to top |
|
 |
exerk |
Posted: Thu Jun 13, 2013 8:52 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
What you are seeing is WMQ queue manager clustering working as advertised. Queue manager clusters load balance messages across instances of a queue depending on the attributes of the queue instances and/or queue managers, e.g. CLWLUSEQ.
Messages (generally) are discrete messages, i.e. a single WMQ message encapsulates all the payload to be sent, however, it is also possible to split payload across multiple messages and form the messages into a group, possibly what you are alluding to in this statement "...if there are 5 members in a cluster then each member will receive only 3 messages hence the application accessing the cluster member will not be having whole message but a part of the message..."?
Perhaps it would be easier for you to understand the mechanism by creating a third queue manager (call it PARIS maybe?) and adding it to the cluster, defining an instance of INVENTORY.QUEUE in the LONDON and NEWYORK queue managers only, and sending messages to the queue from the new queue manager. You can then play around with the BIND_NOT_FIXED and BIND_ON_OPEN attributes of the queues to see what happens. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jun 13, 2013 8:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Sach wrote: |
The reason why i am asking whether the behavior is correct or because as per the sample setup provided by IBM, it is mentioned that messages sent on LONDON QMGR will be available on NEWYORK QMGR |
Post that quote. Messages are only available on the queue manager to which they've been delivered. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
hughson |
Posted: Fri Jun 14, 2013 8:01 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
Sach wrote: |
The problem i am facing is i am putting 15 messages into the queue INVENTQ on LONDON QMGR which is part of the cluster, When i check the messages available on NEWYORK QMGR i see that the messages 1,3,5,7,9,11,13 and 15 being available and when i check on LONDON QMGR i see the messages 2,4,6,8,10,12 and 14. I wanted to know if this is the expected behavior and is there any way by which all messages sent into INVENTQ from LONDON QMGR be available on NEWYORK QMGR because as per this scenario say if there are 5 members in a cluster then each member will receive only 3 messages hence the application accessing the cluster member will not be having whole message but a part of the message. Please correct me if i am wrong somewhere as i am new to MQ and still learning. |
When I read the above, it makes me think you were hoping to see all 15 messages on the INVENTQ on the LONDON QMgr *AND* all 15 messages on the INVENTQ on the NEWYORK QMgr. Is this the behaviour you were hoping for?
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|