| Author |
Message
|
| bernard_fay |
 Posted: Tue Jan 22, 2013 12:36 pm Post subject: binding, retrying, ... |
 |
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
Hello,
I setup a two nodes MQ cluster for which the cluster channels were working fine until I restarted one of the servers. After the reboot the cluster-sender channel on both servers are unable to reconnect going from binding to retrying.
In the event viewer, we have the following events:
Event ID 9202
1/22/2013 14:55:56 - Process(2596.10) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(MQ3) Installation(Installation1) VRMF(7.5.0.0) QMgr(QM3)
Remote host 'MQ2 (192.168.56.102) (1414)' not available, retry later.
The attempt to allocate a conversation using TCP/IP to host 'MQ2 (192.168.56.102) (1414)' for channel TO.QM2 was not successful. However the error may be a transitory one and it may be possible to successfully allocate a TCP/IP conversation later. &P In some cases the remote host cannot be determined and so is shown as '????'.
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 10061 (X'274D'). 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 'MQ2 (192.168.56.102) (1414)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again.
Event ID 9999
1/22/2013 14:55:56 - Process(2596.10) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(MQ3) Installation(Installation1) VRMF(7.5.0.0) QMgr(QM3)
Channel 'TO.QM2' to host '192.168.56.102' ended abnormally.
The channel program running under process ID 2596(3028) for channel 'TO.QM2' ended abnormally. The host name is '192.168.56.102'; in some cases the host name cannot be determined and so is shown as '????'.
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.
I am surprised to see (192.168.56.102) (1414) while the listeners have been defined for port 51414. A display channel shows the defined port (51414) for listeners.
In the forum I saw a stop force on the cluster-receiver channel but that did not change anything.
Does someone have a clue about the cause of this problem?
Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jan 22, 2013 1:16 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
Are your listeners running?
_________________
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 |
|
|
| PeterPotkay |
| Posted: Tue Jan 22, 2013 2:16 pm Post subject: Re: binding, retrying, ... |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
| bernard_fay wrote: |
I am surprised to see (192.168.56.102) (1414) while the listeners have been defined for port 51414. A display channel shows the defined port (51414) for listeners. |
Using runmqsc commands, display your CLUSRCVR channel definitions and post the output here.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 22, 2013 9:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Looks like you changed the port on the cluster receiver channel without following proper procedure.
I believe the procedure is outlined both in the cluster manual and again somewhere on this forum (posts within the last 18 months?)
Perform the change again, following proper procedure.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bernard_fay |
| Posted: Wed Jan 23, 2013 5:03 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
I didn't "change" the port numbers, I defined the port numbers while creating the queue managers.
Here is the output for one of the cluster-receiver channel:
| Code: |
DISPLAY CHANNEL (TO.QM2) TYPE(CLUSRCVR)
2 : DISPLAY CHANNEL (TO.QM2) TYPE(CLUSRCVR)
AMQ8414: Display Channel details.
CHANNEL(TO.QM2) CHLTYPE(CLUSRCVR)
ALTDATE(2013-01-22) ALTTIME(09.22.16)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CLUSNL( ) CLUSTER(NEWCLUSTER)
CLWLPRTY(0) CLWLRANK(0)
CLWLWGHT(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME( )
CONVERT(NO) DESCR( )
DISCINT(0) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(THREAD) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MRDATA( ) MREXIT( )
MRRTY(10) MRTMR(1000)
MSGDATA( ) MSGEXIT( )
NETPRTY(0) NPMSPEED(FAST)
PROPCTL(COMPAT) PUTAUT(DEF)
RCVDATA( ) RCVEXIT( )
RESETSEQ(NO) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SEQWRAP(999999999)
SHORTRTY(10) SHORTTMR(60)
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USEDLQ(YES) |
This is a test environment so we can try different things without problem.
Thanks, |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Jan 23, 2013 5:40 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| I can not remember 10% but dont you have to specify an entry in the CONNAME on the cluster receiver? |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 23, 2013 5:54 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| rammer wrote: |
| I can not remember 10% but dont you have to specify an entry in the CONNAME on the cluster receiver? |
From the Info Centre:
"...This parameter is required for channels with a channel type (CHLTYPE) of SDR, RQSTR, CLNTCONN, and CLUSSDR. It is optional for SVR channels, and for CLUSRCVR channels of TRPTYPE(TCP) (the port must be 1414 if the CONNAME parameter is not used)..."
I suspect the OP is hitting the issue due to the red-highlighted section above.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bernard_fay |
| Posted: Wed Jan 23, 2013 6:20 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
Exerk,
| Quote: |
"...This parameter is required for channels with a channel type (CHLTYPE) of SDR, RQSTR, CLNTCONN, and CLUSSDR. It is optional for SVR channels, and for CLUSRCVR channels of TRPTYPE(TCP) (the port must be 1414 if the CONNAME parameter is not used)..." |
Does that mean we are forced to use port 1414? If yes, I will have a problem with the security people. 
Thanks, |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 23, 2013 6:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bernard_fay wrote: |
Exerk,
| Quote: |
"...This parameter is required for channels with a channel type (CHLTYPE) of SDR, RQSTR, CLNTCONN, and CLUSSDR. It is optional for SVR channels, and for CLUSRCVR channels of TRPTYPE(TCP) (the port must be 1414 if the CONNAME parameter is not used)..." |
Does that mean we are forced to use port 1414? If yes, I will have a problem with the security people.
Thanks, |
No, it means you need to set CONNAME if you're not using port 1414. |
|
| Back to top |
|
|
| bernard_fay |
| Posted: Wed Jan 23, 2013 6:33 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
I am puzzled... The help says:
| Quote: |
For all types of channel except cluster-receiver channels, type the name of the computer that hosts the target queue manager. The format of the connection name depends on the transmission protocol that is selected. For example, if you are using the TCP/IP protocol and you know that the target queue manager is connecting using a port number other than the WebSphere® MQ default of 1414, type computer_name(port_number), where computer_name is the name or IP address of the computer that hosts the target queue manager, and port_number is the port that the target queue manager's listener is using.
For cluster-receiver channels on Windows, UNIX and Linux, that use the TCP/IP transport protocol, do not specify a value for this attribute; WebSphere MQ generates a name for using, assuming the default port and the current IPv4 address of the system. If the system does not have an IPv4 address, the current IPv6 address of the system is used. For cluster-receiver channels on other platforms, and for cluster-receiver channels that do not use the TCP/IP transport protocol, type the name of the computer that hosts the local queue manager. |
But tried it anyway, so I did :
| Quote: |
| ALTER CHANNEL(TO.QM2) CHLTYPE(CLUSRCVR) CONNAME('192.168.56.102(51414)') |
I did a force stop on the cluster-receiver channel, stopped and restarted the cluster-sender channel, I restarted the cluster-receiver channel. Still binding, retrying...
Thanks, |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 23, 2013 6:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 23, 2013 6:42 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7717
|
|
| Back to top |
|
|
| bernard_fay |
| Posted: Wed Jan 23, 2013 7:35 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
To mqjeff and PeterPotkay, I saw your links and that's what I did. I almost followed this procedure, almost because I did the creation of the cluster with the WMQ Explorer.
Maybe I found something. The display of receiver channel:
| Quote: |
DIS CLUSQMGR(*) DEFTYPE WHERE(CHANNEL EQ TO.QM2)
1 : DIS CLUSQMGR(*) DEFTYPE WHERE(CHANNEL EQ TO.QM2)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(QM2) CHANNEL(TO.QM2)
CLUSTER(NEWCLUSTER) DEFTYPE(CLUSRCVR) |
The display of the sender channel:
| Quote: |
DIS CLUSQMGR(*) DEFTYPE WHERE(CHANNEL EQ TO.QM2)
23 : DIS CLUSQMGR(*) DEFTYPE WHERE(CHANNEL EQ TO.QM2)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(QM2) CHANNEL(TO.QM2)
CLUSTER(NEWCLUSTER) DEFTYPE(CLUSSDRB) |
If I understand, DEFTYPE(CLUSSDRB) means the cluster-sender channel is using a auto-defined channel, which is not the case, while the cluster-receiver channel is using a manual definition.
I think I should change the DEFTYPE of the receiver channel. Does it make sense? If yes, I can't find how to do it.
Thanks, |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 23, 2013 7:40 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bernard_fay wrote: |
| ...I think I should change the DEFTYPE of the receiver channel... |
Again, from the Info Centre:
| Quote: |
CLUSSDR
Defined explicitly as a cluster-sender channel
CLUSSDRA
Defined by auto-definition as a cluster-sender channel
CLUSSDRB
Defined as a cluster-sender channel, both explicitly and by auto-definition
CLUSRCVR
Defined as a cluster-receiver channel |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bernard_fay |
| Posted: Wed Jan 23, 2013 7:40 am Post subject: |
|
|
Apprentice
Joined: 24 Jul 2012
Posts: 30
|
Oupss...
| Quote: |
I think I should change the DEFTYPE of the receiver channel. Does it make sense? If yes, I can't find how to do it. |
I mean the DEFTYPE of the sender channel. |
|
| Back to top |
|
|
|
|
