| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting channel negotiation failed error AMQ9575E |
« View previous topic :: View next topic » |
| Author |
Message
|
| SivakumarAkkupalli |
 Posted: Tue Jan 04, 2022 6:03 am Post subject: Getting channel negotiation failed error AMQ9575E |
 |
|
Newbie
Joined: 04 Jan 2022
Posts: 3
|
Hi All,
App teams using svr conn channel to connect to the Queue manager. They are facing issue , app not able to connect to queue manager sometimes. App disconnect automatically . Post restart of apps, they are able to connect. This happens once a week or twice a week. Checked MQ logs got Channel channel negotiation failed error for that svr conn channel. Please let me know if any have solution for this. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jan 04, 2022 8:22 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to General Discussion forum.
Please post the complete errors found in the error logs for the qmgr and client platform.
_________________
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 |
|
|
| SivakumarAkkupalli |
| Posted: Wed Jan 05, 2022 5:46 am Post subject: |
|
|
Newbie
Joined: 04 Jan 2022
Posts: 3
|
AMQ9575E: Negotiation failed for channel
EXPLANATION:
A channel between the local queue manager and the remote end could not be
established due to a negotiation failure. The failure was such that the channel
name could not be determined. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 05, 2022 8:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please provide a bit more detail.
I asked you to post errors from BOTH ends. What error(s) did you see in the error logs on the client end?
Is this a new application? Has it ever worked before? What programming language?
What o/s at the client? What MQ qmgr v/r/m/f?
_________________
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 |
|
|
| SivakumarAkkupalli |
| Posted: Thu Jan 06, 2022 6:09 am Post subject: |
|
|
Newbie
Joined: 04 Jan 2022
Posts: 3
|
Hey,
Client end they are getting mqrc 2538.
It is working earlier and now also post restart of apps. Intermittently they are facing issue.
It is java application on client slide.
QMGR running in 9.0.0.5 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jan 06, 2022 7:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| hughson |
| Posted: Mon Jan 10, 2022 2:03 am Post subject: Re: Getting channel negotiation failed error AMQ9575E |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| SivakumarAkkupalli wrote: |
| Checked MQ logs got Channel channel negotiation failed error for that svr conn channel. Please let me know if any have solution for this. |
| SivakumarAkkupalli wrote: |
AMQ9575E: Negotiation failed for channel
EXPLANATION:
A channel between the local queue manager and the remote end could not be
established due to a negotiation failure. The failure was such that the channel
name could not be determined. |
Given that this error message does not include the channel name, can you let us know how you know that this error is for your SVRCONN channel? Did you, for example, match up the times? Do you only have one channel going into this queue manager so it can only be this SVRCONN? Or something else.
The reason I ask is that the error you are getting at the client side of the connection is 2538 (MQRC_HOST_NOT_AVAILABLE) which means the client connection attempt was not able to reach the queue manager, so it seems unlikely that the queue manager would have anything in its error log to go with this client side reason code because the client could not reach the host.
Can you tell us a little more about how your client application is configured? Do you use a hostname or an IP address, do you have a list of them or just a single one? When the error occurs can you ping the same hostname/IP address. You suggest that it is fixed by restarting the application, which suggests the outage is very short-lived? This also means that the application could catch this reason code and reconnect itself and you wouldn't have to restart it. Have you spoken to the people who manage your network about these outages?
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
|
|
|
|
