| Author |
Message
|
| NayanK |
 Posted: Mon Aug 16, 2004 2:30 am Post subject: Sender Channel Retrying |
 |
|
Newbie
Joined: 16 Aug 2004
Posts: 4
|
We are facing a peculiar problem on a live site.
We have a server A which communicates with server B over IBM MQ Websphere 5.3.
The Sender Channel on A goes into Retrying mode and cannot be brought into running state.
We have tried PING it says ping is successfull. We have tried Resolve also but no success.
However the Sender channel on B is running and is able to transmit messages succesfully to A. |
|
| Back to top |
|
 |
| obriencm |
| Posted: Mon Aug 16, 2004 3:51 am Post subject: |
|
|
Acolyte
Joined: 31 Jan 2002
Posts: 64
Location: Ireland
|
| Are there any errors showing up in the log on either side? |
|
| Back to top |
|
|
| NayanK |
| Posted: Mon Aug 16, 2004 4:12 am Post subject: Sender Side Error |
|
|
Newbie
Joined: 16 Aug 2004
Posts: 4
|
08/16/2004 12:35:14
AMQ9526: Message sequence number error for channel 'TO.PIQMGR'.
EXPLANATION:
The local and remote queue managers do not agree on the next message sequence
number. A message with sequence number 591 has been sent when sequence number
1 was expected.
ACTION:
Determine the cause of the inconsistency. It could be that the synchronization
information has become damaged, or has been backed out to a previous version.
If the situation cannot be resolved, the sequence number can be manually reset
at the sending end of the channel using the RESET CHANNEL command.
----- amqrfpta.c : 334 --------------------------------------------------------
08/16/2004 12:35:15
AMQ9506: Message receipt confirmation failed.
EXPLANATION:
Channel 'TO.PIQMGR' has ended because the remote queue manager did not accept
the last batch of messages.
ACTION:
The error log for the channel at the remote site will contain an explanation of
the failure. Contact the remote Systems Administrator to resolve the problem.
----- amqrmrca.c : 670 --------------------------------------------------------
08/16/2004 12:35:15
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.PIQMGR' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.PIQMGR' in the error
files to determine the cause of the failure. |
|
| Back to top |
|
|
| obriencm |
| Posted: Mon Aug 16, 2004 5:12 am Post subject: Solution |
|
|
Acolyte
Joined: 31 Jan 2002
Posts: 64
Location: Ireland
|
Hi there,
The problem is a sequencing one, you need to stop the "TO.PIQMGR" sender chl. you then need to reset the messgae number to 1. once you restart the channel your issue should be resolved.
Hope this helps. |
|
| Back to top |
|
|
| NayanK |
| Posted: Mon Aug 16, 2004 5:15 am Post subject: Sequence reset |
|
|
Newbie
Joined: 16 Aug 2004
Posts: 4
|
| I forgot to mention that we have tried that, but still it does not get resolved. |
|
| Back to top |
|
|
| obriencm |
| Posted: Mon Aug 16, 2004 5:19 am Post subject: |
|
|
Acolyte
Joined: 31 Jan 2002
Posts: 64
Location: Ireland
|
| Are there any errors showing on the reciever channel side? |
|
| Back to top |
|
|
| NayanK |
| Posted: Mon Aug 16, 2004 5:34 am Post subject: Receiver Side Errors |
|
|
Newbie
Joined: 16 Aug 2004
Posts: 4
|
----- amqccita.c : 973 --------------------------------------------------------
08/16/2004 11:23:09
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.HOSTQMGR' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.HOSTQMGR' in the error
files to determine the cause of the failure.
----- amqrccca.c : 804 --------------------------------------------------------
08/16/2004 11:23:41
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'TO.HOSTQMGR' started.
ACTION:
None.
-------------------------------------------------------------------------------
08/16/2004 11:23:46
AMQ9208: Error on receive from host 172.25.100.27.
EXPLANATION:
An error occurred receiving data from 172.25.100.27 over TCP/IP. This may be
due to a communications failure.
ACTION:
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
values and tell the systems administrator.
----- amqccita.c : 2761 -------------------------------------------------------
08/16/2004 11:23:46
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.
----- amqrmrsa.c : 461 --------------------------------------------------------
08/16/2004 11:23:51
AMQ9208: Error on receive from host 172.25.100.27.
EXPLANATION:
An error occurred receiving data from 172.25.100.27 over TCP/IP. This may be
due to a communications failure.
ACTION:
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
values and tell the systems administrator.
----- amqccita.c : 2761 -------------------------------------------------------
08/16/2004 11:23:51
AMQ9228: The TCP/IP responder program could not be started.
EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Aug 16, 2004 5:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Try a search on 10054 (X'2746') or MQNOREMPOOL if you are using a windows box. You will get lots of hits |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Aug 20, 2004 4:15 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| 10054 is ECONNRESET, which just means a general network problem. No WMQ problem here - don't shoot the messenger! |
|
| Back to top |
|
|
| offshore |
| Posted: Fri Aug 20, 2004 6:47 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
NayanK,
10054 is almost always a network problem. Have the network guys check firewalls, switches, routers anything between point A and Point B.
Aside from that:
1.] Has the 2 QMGRS talked before?
2.] From the QMGR that the sender channel goes into "RETRY" have you tried to telnet to the destination box to see if you can make it?
If QMGR_A channel goes into retry issue a telnet to the destinations mq listener port.
Offshore |
|
| Back to top |
|
|
|
|
