| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Sender channel in retrying mode without reason |
« View previous topic :: View next topic » |
| Author |
Message
|
| matth |
 Posted: Wed Jan 31, 2018 10:13 am Post subject: Sender channel in retrying mode without reason |
 |
|
Apprentice
Joined: 13 Feb 2007
Posts: 44
Location: Brazil
|
Hi:
I have an MQSeries (8.0.0.5) runining on Windows machine. I had some issue with one sender channel which entered in retrying mode. In log files, there is no reason, but shows an attempt to start it, as below:
-------------------------------------------------------
1/30/2018 11:57:00 - Process(8968.1) User(MUSR_MQADMIN) Program(amqrcmla.exe)
Host(A) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM.A)
AMQ9514: Channel 'CA.TO.B' is in use.
EXPLANATION:
The requested operation failed because channel 'CA.TO.B' is
currently active.
ACTION:
Either end the channel manually, or wait for it to close, and retry the
operation.
These attempts to start weren´t made by user request, due there is not Start command attempts on log file.
After some minutes, channel has become to Running state without intervention.
Unfortunately, I don´t have acess to Queue Manager on B side or any log files on this side. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Jan 31, 2018 10:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
A channel will retry for a variety of reasons, and will continue to retry according to the retry attributes of the channel. What info in the error log precedes the entry you posted?
_________________
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 |
|
|
| matth |
| Posted: Fri Feb 09, 2018 5:48 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007
Posts: 44
Location: Brazil
|
| bruce2359 wrote: |
| A channel will retry for a variety of reasons, and will continue to retry according to the retry attributes of the channel. What info in the error log precedes the entry you posted? |
Ok. A side said that he tried some "start" options, with no success, but log didn´t register any root-cause to channel becomes in Retrying State.
On B side, customer said that all channels (receiver) were in Running state (which I believe to be impossible).
Att, |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 09, 2018 6:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Reasonably clear from the log that AMQ9514: Channel 'CA.TO.B' is in use.
Gather some information:
On both A and B, issue the MQSC DISPLAY CHSTATUS(CA.TO.B) COMMAND. Post results here - not the 'he said' kind.
Stop both ends of the channel, with MODE(FORCE), if necessary. From the non-started SDR channel issue the MQSC PING CHL(channelname) command. Again, post results here.
_________________
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 |
|
|
| matth |
| Posted: Fri Feb 09, 2018 8:15 am Post subject: |
|
|
Apprentice
Joined: 13 Feb 2007
Posts: 44
Location: Brazil
|
| bruce2359 wrote: |
Reasonably clear from the log that AMQ9514: Channel 'CA.TO.B' is in use.
Gather some information:
On both A and B, issue the MQSC DISPLAY CHSTATUS(CA.TO.B) COMMAND. Post results here - not the 'he said' kind.
Stop both ends of the channel, with MODE(FORCE), if necessary. From the non-started SDR channel issue the MQSC PING CHL(channelname) command. Again, post results here. |
This was an temporary situation, which I couldn´t replicate. I just wanted to understand this one. I only have access to A side data and logs. On this one, I had no information about retrying status, but receved an PrintScreen of MQExplorer which proves Retrying stante of channel.
Att, |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 09, 2018 9:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Read up on problem determination with mq channels here: http://www-01.ibm.com/support/docview.wss?uid=swg21620770
Retry state means that the channel retry software is waiting for the current retry interval (wait) to expire.
Is this a frequent occurrence? Occasional? Rare?
Next time, issue the STOP CHANNEL(CA.TO.B) command. When the channel goes to STOPPED state, issue the MQSC PING CHANNEL(CA.TO.B) command. Post the results here.
I'm pre-configured to be suspicious of the folks at the receiver end of of a channel in retry. But that's just me.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
