| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9528W: User requested channel 'XXXXX.XXXX' to be stopped. |
« View previous topic :: View next topic » |
| Author |
Message
|
| swatkats |
 Posted: Fri Aug 04, 2023 7:34 pm Post subject: AMQ9528W: User requested channel 'XXXXX.XXXX' to be stopped. |
 |
|
Novice
Joined: 22 May 2010
Posts: 20
|
Recently upgraded to 9.3.0.4, heavily loaded 3 partner sender channels from 3 different systems from same datacenter reported TCP/IP timeouts on 3 different occasions while trying to send messages to this upgraded systems. there is no pattern.
upon checking the upgraded system, we could see AMQ9528W: User requested channel 'XXXXX.XXXX' to be stopped. whereas there was no manual stop was ever involved.
no FDC's. Trying to understand why same 3 senders fail connecting to the upgraded system with same error each time.
Only commonality is all three senders have heavy traffic(for MQ its not heavy) but in comparison to the other partners connecting to the upgraded system that never failed.
Anyone have come across with "AMQ9528W: User requested channel 'XXXXX.XXXX' to be stopped" whereas without significant evidence of manual stop/Kill/FDC's? could be a bug? thoughts please.
I have IBM looking into my case but need your expert views. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sat Aug 05, 2023 7:39 am Post subject: Re: AMQ9528W: User requested channel 'XXXXX.XXXX' to be stop |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.
|
| swatkats wrote: |
| ... upon checking the upgraded system, we could see AMQ9528W: User requested channel 'XXXXX.XXXX' to be stopped. whereas there was no manual stop was ever involved. |
Any other errors written to the log at either/both ends of the channel? Channel Events enabled at both ends of the channel?
_________________
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 |
|
|
| abhi_thri |
| Posted: Thu Aug 10, 2023 1:46 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
|
| Back to top |
|
|
| swatkats |
| Posted: Thu Aug 24, 2023 7:47 am Post subject: |
|
|
Novice
Joined: 22 May 2010
Posts: 20
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 24, 2023 8:42 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.
|
When you opened a PMR with IBM, what was their solution?
_________________
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 |
|
|
| gbaddeley |
| Posted: Thu Aug 24, 2023 5:19 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2495
Location: Melbourne, Australia
|
I think IBM means that someone issued MQSC or PCF to stop the channel. This invokes the amqrcmla process to handle the stop and update the channel status table. I believe amqrcmla was introduced in MQ v6.0.
_________________
Glenn |
|
| 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
|
|
|
|
