| Author |
Message
|
| cjcausaren |
 Posted: Mon Jul 13, 2015 7:11 pm Post subject: MQ Sender Channel Retrying |
 |
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
Hi,
Seeking for your assistance. I always got an a retying status in sender channel. I tried to stop/start, reset the channels but seems it has the same result. the receiver channel in target server are currently with inactive status. But if we're retrying to start it, the status doesnt change.
Hoping for your feedback!
Thank you
|
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Jul 13, 2015 8:40 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Can you use the MQ PING CHANNEL command from the non-started (STOPPED or INACTIVE) sender end? Is it successful? If not, then definitions at both ends are incompatible.
Can you do a successful tcpip ping from the sender end to the receiver end? If not, there is a likely a firewall issue.
If you can successfully do a tcpip ping from sender to receiver, then look to make sure that there is a listener running on the receiver end. AND that the sender definition CONNAME attribute specifies both ip address and port number.
_________________
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 |
|
|
| PaulClarke |
| Posted: Mon Jul 13, 2015 8:52 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Every time a channel RETRIES it will write a message to the error log explaining why it is failing to start. Have you looked in AMQERR01.LOG for the problem ?
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jul 13, 2015 10:25 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Can you please add information such as
- Platform at both ends
- Version on MQ at both ends including the FixPack level
- Can you ping/telnet to the destination IP address & port?
- Post the channel and init queue definitions (for both SDR & RCVR)
We aim to help you help yourself in resolving the problem.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 14, 2015 4:40 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
On the channel status... is the channel "in doubt" ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| cjcausaren |
| Posted: Tue Jul 14, 2015 5:42 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
Hi Everyone,
I tried to use the MQ PING command and it gave a result:
PING CHANNEL(channel-name)
4 : PING CHANNEL(channel-name)
AMQ9202: Remote host '' not available, retry later.
TCP/IP PING Result:
ID@Server:/home/user # ping <IP address> <PORT>
PING <IP address>: (<IP address>): <PORT> data bytes
1423 bytes from (<IP address>): icmp_seq=0 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=1 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=2 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=3 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=4 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=5 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=6 ttl=255 time=0 ms
1423 bytes from (<IP address>): icmp_seq=7 ttl=255 time=0 ms
--- <IP> ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Jul 14, 2015 8:43 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Well, the first thing to do is to double check that you have correctly specified the IP address in the CHANNEL CONNNAME() field. The second thing to check is that you have definitely started the listener on the target machine.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| cjcausaren |
| Posted: Tue Jul 14, 2015 8:55 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
Thanks Paul,
I'll try to recheck the CONNNAME of both channels, as I checked the logs it seem it doesnt connecting to the target server
AMQ9002: Channel '<channel name>' is starting.
EXPLANATION:
Channel '<channel name>' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
07/15/15 00:47:49 - Process(19071004.1) User(<USER>) Program(runmqchl)
Host(HOSTNAME) Installation(Installation1)
VRMF(7.1.0.0) QMgr(<Queuemanager name>)
AMQ9202: Remote host '' not available, retry later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host '' for channel
<channel name> was not successful. However the error may be a transitory one
and it may be possible to successfully allocate a TCP/IP conversation later.
In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is 0
(X'0'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host ''
was not running. If this is the case, perform the relevant operations to start
the TCP/IP listening program, and try again.
----- amqccita.c : 1423 -------------------------------------------------------
07/15/15 00:47:49 - Process(19071004.1) User(<USER>) Program(runmqchl)
Host(HOSTNAME) Installation(Installation1)
VRMF(7.1.0.0) QMgr(<Queuemanager name>)
AMQ9999: Channel '<channel name>' to host '<destination IP(port)>' ended
abnormally.
EXPLANATION:
The channel program running under process ID 19071004 for channel
'<channel name>' ended abnormally. The host name is '<destination IP(port)>';
in some cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide. |
|
| Back to top |
|
|
| cjcausaren |
| Posted: Wed Jul 15, 2015 3:31 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
Hi
Would like to ask if youre altering listener port, is there a additional process to start/activate it??
because when I changed the default port 1414 to 1515. The Listener throws AMQ8147: WebSphere MQ object * not found.
Hoping for your feedback 
Thanks! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 15, 2015 3:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| cjcausaren wrote: |
Hi
Would like to ask if youre altering listener port, is there a additional process to start/activate it??
because when I changed the default port 1414 to 1515. The Listener throws AMQ8147: WebSphere MQ object * not found.
Hoping for your feedback
Thanks! |
When you changed the the default port of what? The listener object itself? The SENDER channel? Post the command you used.
Post the SENDER channel definition.
Post the RECEIVER channel definition.
_________________
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 |
|
|
| fjb_saper |
| Posted: Wed Jul 15, 2015 11:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| cjcausaren wrote: |
Hi
Would like to ask if youre altering listener port, is there a additional process to start/activate it??
because when I changed the default port 1414 to 1515. The Listener throws AMQ8147: WebSphere MQ object * not found.
Hoping for your feedback
Thanks! |
Did you try a telnet?
| Code: |
| telnet mqserverhost mqlistenerport |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jul 15, 2015 11:48 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| bruce2359 wrote: |
Post the SENDER channel definition.
Post the RECEIVER channel definition. |
I asked this same question several days ago but so far nothing has been forthcoming.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| cjcausaren |
| Posted: Wed Jul 15, 2015 4:24 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
| bruce2359 wrote: |
| cjcausaren wrote: |
Hi
Would like to ask if youre altering listener port, is there a additional process to start/activate it??
because when I changed the default port 1414 to 1515. The Listener throws AMQ8147: WebSphere MQ object * not found.
Hoping for your feedback
Thanks! |
When you changed the the default port of what? The listener object itself? The SENDER channel? Post the command you used.
Post the SENDER channel definition.
Post the RECEIVER channel definition. |
Hi, its for listener object itself, I used ALTER LISTENER(listnername) TRPTYPE(TCP) PORT(1515)
Last edited by cjcausaren on Wed Jul 15, 2015 5:17 pm; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 15, 2015 4:45 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| cjcausaren wrote: |
PING CHANNEL(channel-name)
4 : PING CHANNEL(channel-name)
AMQ9202: Remote host '' not available, retry later. |
Excellent so far. With the TCP ping command ou have demonstrated that the sender end of the network can see the receiver end of the network.
Your attempt to do an MQ PING has demonstrated that your definitions of the SENDER channel specify an incorrect ipaddress OR a listener port that is not running on the receiver end of the channel.
Did you define a LISTENER object at the receiver end? Or did you start an instance of runmqlsr at the receiver end of the channel? Is the listener running? What port is it listening on? Prove your answer by posting the LISTENER object definition and its current state; OR the runmqlsr command that you used to start the listener.
You have been asked more than one time to post your definitions of both SENDER and RECEIVER channels. Why have you not done so? We are trying to help you, but you seem unable or unwilling to provide the information we need to help you
_________________
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 |
|
|
| cjcausaren |
| Posted: Wed Jul 15, 2015 5:39 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 6
|
Last edited by cjcausaren on Thu Jul 16, 2015 12:25 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
