| Author |
Message
|
| maja |
 Posted: Wed Sep 26, 2007 3:15 pm Post subject: |
 |
|
Apprentice
Joined: 13 Jun 2006
Posts: 30
|
Hilltops,
Thanks a lot for the quick response.
That does answer my question.
Thank you all ....I will update the results on the forum after implementation.
Regards,
Maja. |
|
| Back to top |
|
 |
| maja |
| Posted: Mon Dec 03, 2007 4:57 pm Post subject: |
|
|
Apprentice
Joined: 13 Jun 2006
Posts: 30
|
hi,
I have pointed the MQ client MQSERVER variable to the VIP of the F5 server, and have the port exposed by the F5 mentioned in the port i.e.
MQSERVER - SYSTEM.ADMIN.SVRXX/TCP/VIP(port)
The Queue Managers on both the servers are running and both are in cluster as QUEUEM1 and QUEUEM2,
When I try to connect to teh server using the client , it returns 2059.
The UID is part of MQM, so access is not the problem.
Please advise what could be the problem, do I need to do anything additional for the connection to MQ server form client through the load balancer.
Thanks,
Maja. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Dec 03, 2007 5:31 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
prove it works via telnet first.
open a command prompt and type:
and tell us the results.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Dec 04, 2007 6:19 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm, interesting.
So I did a test to see if you could indeed connect *whatever as the QMGR name and use MQSERVER. Why yes you can. Doing this allows you to connect to whatever QMGR might happen to answer at that IP and port.
I would guess that if the IP is not changed once the connection is made, then you will be OK. Do yourself a favor, NEVER create more then one QMGR with a particular name.
So maja, if you are doing request/reply and you loose your connection, how do you plan to reconnect to the correct QMGR to get your reply?
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 04, 2007 8:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| JosephGramig wrote: |
| So maja, if you are doing request/reply and you loose your connection, how do you plan to reconnect to the correct QMGR to get your reply? |
I think Jospeh just burst this bubble. 
The only way around this that I can think of is quite convoluted. On the MQPUT of the request, you will know what QM you are connected to. It will be in the MQMD_ReplyToQueueManager field after the MQPUT(1). I suppose you could also MQINQ the QM after establishing the initial connection.
But just knowing the QM name is not enough on subsequent connection attempts. The load balancer will not care that you want to go to QM1 if you specify the VIP. You would have to maintain an internal table of QMs and their direct IPs and use that (bypassing the VIP) if you wanted to directly connect to a particular QM behing the load balancer. 
Doable, but ugly. Don't use IP load balancers with MQ.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| maja |
| Posted: Tue Dec 04, 2007 9:16 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2006
Posts: 30
|
Hi,
Thanks for the inputs.
The Load balancer points the client to the proper queue manager.
It points the same client ot the same queue manager as long as the earlier Queue manager is not available. Thats what I was told.
Yet to reach that point, as basic connection is not working.
Thanks,
Maja. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 04, 2007 9:20 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| maja wrote: |
The Load balancer points the client to the proper queue manager.
|
How could a load balancer know what the proper QM is?
| maja wrote: |
| It points the same client ot the same queue manager as long as the earlier Queue manager is not available. |
And what happens when both QMs are up, your new connections are being load balanced, but you need to go to a particular QM because that's where your reply message is?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| maja |
| Posted: Tue Dec 04, 2007 9:31 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2006
Posts: 30
|
Peter,
Telnet Session works.
Please advise.
Thanks,
Maja. |
|
| Back to top |
|
|
| maja |
| Posted: Tue Dec 04, 2007 9:33 am Post subject: |
|
|
Apprentice
Joined: 13 Jun 2006
Posts: 30
|
Load Balancer uses teh client IP and points all the requests from particular IP to the same Queue manager.
So if Client sends request, it reaches LB, it has the client IP now, so the response request query for this client IP would be done to the same queue manager.
Thanks,
Maja. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Dec 04, 2007 12:28 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
maja,
Did you put the * in front of the QMGR name for your MQCONN call?
Consider this scenario, the QMGR1 is down and F5 sends traffic to QMGR2. A request goes out of QMGR2 and the connection is broken. QMGR1 is now up, so when the client attempts a reconnect, it gets QMGR1. Now the client cannot get its reply from QMGR2.
Of course, if you don't attempt to look for replies when your connection gets broken, then I guess you would be OK.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 04, 2007 4:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Isn't this done just as easily with a client channel table? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 04, 2007 6:03 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I don't think this is a problem with what's coded in the MQCONN call (* or blank or something else) If that was the problem, then maja would be getting a 2058. But he says he is getting a 2059, which to me says his connection attempt is being routed to an IP / port where there is no QM listening, or its trying to get to the correct IP /port but not getting all the way there, or if he is, the QM isn't accepting any more connections (Max Channels hit, security exit blocking the call, etc)
What's puzzling is that telnet is working.
maja, post exactly what you did for the telnet test. You did specify the MQ port # on the telnet test, right?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 04, 2007 6:05 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
| Isn't this done just as easily with a client channel table? |
Client channel tables will always send you to the 1st available QM following the search rules for eligible QMs in the table. It won't load balance new connections.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
