| Author |
Message
|
| nsmq |
 Posted: Wed Apr 05, 2023 9:08 am Post subject: Failure to connect to an MQ Manger through a load balancer |
 |
|
Newbie
Joined: 05 Apr 2023
Posts: 2
|
Hi Everyone,
I need help from you. I have an issue when a client want to connect to an MQ Manager through a load balancer. this issue doesn't appear when it connect directly to an MQ manager. after analyzing this issue, we see that the client tries to connect by its username/paswword and the load balancer it forward these creds but the IBM MQ respond with the error: 2035 MQRC_NOT_AUTHORIZED but when we try to connect directly to MQ Manager with same creds it work fine. any help from you.
thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Apr 05, 2023 2:44 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.
|
Where do you see the 2035 error?
What error is written to the qmgr error logs?
A load balancer? Which one? Has this ever worked before? What changed?
_________________
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 |
|
|
| nsmq |
| Posted: Wed Apr 05, 2023 4:56 pm Post subject: |
|
|
Newbie
Joined: 05 Apr 2023
Posts: 2
|
thanks for your reply and your attention
I see it in the network traffic between load balancer netscaler and and mq manager after load balancer forward the user ID and password sent by the mq client and get response ith this error
I'm not an admin for IBM MQ manager and I don't have access to it just I have access to the load balancer and I want to load balance between these mq manager.
This is the first time that we load balance these solution mq manager. the issue occur just when we connect through netscaler but when we connect directly it work. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Apr 06, 2023 3:31 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| nsmq wrote: |
| I'm not an admin for IBM MQ manager and I don't have access to it just I have access to the load balancer and I want to load balance between these mq manager. |
It will be very difficult to diagnose this problem without being able to see the queue manager error log. In short you will have to guess every possible problem instead of just taking one look at the log and being told EXACTLY what the problem is. Suggest you make friends with your Queue manager Admins.
| nsmq wrote: |
| This is the first time that we load balance these solution mq manager. the issue occur just when we connect through netscaler but when we connect directly it work. |
One GUESS could be that the queue manager is checking the IP address presented with the user ID/password and if the client is not from the expected IP address it is bounced. Going through netscaler could mean you are presenting a different IP address than going directly. To fix this you will need to talk to your Queue Manager Administrator.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 06, 2023 6:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.
|
| nsmq wrote: |
| This is the first time that we load balance these solution mq manager. the issue occur just when we connect through netscaler but when we connect directly it work. |
Working successfully without netscaler, failing with netscaler. Seems to suggest netscaler configuration issue.
_________________
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 |
|
|
| zpat |
| Posted: Fri Apr 07, 2023 1:58 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Look at channel events, then add the missing chlauth rule.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
