ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » RETRYING CLUSTER SENDERS dis chstatus shows wrong conname

Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next
 RETRYING CLUSTER SENDERS dis chstatus shows wrong conname « View previous topic :: View next topic » 
Author Message
ivanachukapawn
PostPosted: Wed Mar 16, 2016 7:57 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

Bruce,

You wrote:

From inside your vm, can you successfully TCP/IP ping address 10.55.175.55?

I ran a ping while logged in to the VM.

mqm@localhost.localdomain(/var/mqm/qmgrs/TEST1/errors): ping 10.55.175.55
PING 10.55.175.55 (10.55.175.55) 56(84) bytes of data.
64 bytes from 10.55.175.55: icmp_seq=1 ttl=64 time=0.054 ms
64 bytes from 10.55.175.55: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 10.55.175.55: icmp_seq=3 ttl=64 time=0.023 ms
64 bytes from 10.55.175.55: icmp_seq=4 ttl=64 time=0.040 ms
64 bytes from 10.55.175.55: icmp_seq=5 ttl=64 time=0.040 ms
64 bytes from 10.55.175.55: icmp_seq=6 ttl=64 time=0.035 ms
64 bytes from 10.55.175.55: icmp_seq=7 ttl=64 time=0.017 ms
64 bytes from 10.55.175.55: icmp_seq=8 ttl=64 time=0.025 ms
64 bytes from 10.55.175.55: icmp_seq=9 ttl=64 time=0.018 ms
64 bytes from 10.55.175.55: icmp_seq=10 ttl=64 time=0.029 ms
64 bytes from 10.55.175.55: icmp_seq=11 ttl=64 time=0.477 ms
64 bytes from 10.55.175.55: icmp_seq=12 ttl=64 time=0.037 ms
64 bytes from 10.55.175.55: icmp_seq=13 ttl=64 time=0.038 ms
64 bytes from 10.55.175.55: icmp_seq=14 ttl=64 time=0.039 ms
e64 bytes from 10.55.175.55: icmp_seq=15 ttl=64 time=0.019 ms
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Mar 16, 2016 8:28 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

You showed the cluster sender... what conname info do you have on the corresponding cluster receiver?

Can you show the output of the runmqsc command on both FR's?
Code:
dis clusqmgr(*)

_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ivanachukapawn
PostPosted: Wed Mar 16, 2016 8:33 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

TEST1:

dis clusqmgr (*)
1 : dis clusqmgr (*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(MQTT1) CHANNEL(TO.MQTT1)
CLUSTER(MQ8cluster)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(TEST1) CHANNEL(TO.TEST1)
CLUSTER(MQ8cluster)

MQTT1:

dis clusqmgr (*)
1 : dis clusqmgr (*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(MQTT1) CHANNEL(TO.MQTT1)
CLUSTER(MQ8cluster)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(TEST1) CHANNEL(TO.TEST1)
CLUSTER(MQ8cluster)

and the Cluster Receiver definition on MQTT1:

display channel (TO.MQTT1) ALL
2 : display channel (TO.MQTT1) ALL
AMQ8414: Display Channel details.
CHANNEL(TO.MQTT1) CHLTYPE(CLUSRCVR)
ALTDATE(2016-03-16) ALTTIME(06.51.34)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) CLUSNL( )
CLUSTER(MQ8cluster) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(10.55.175.55(1441)) CONVERT(NO)
DESCR( ) DISCINT(6000)
HBINT(300) KAINT(AUTO)
LOCLADDR(10.55.175.55) 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)
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Mar 16, 2016 12:29 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

Since this is a test environment, I'm going to suggest that you disable CHLAUTH, and remove LOCLADDR() values from both channel defs.

If/when the channels fail again, post the entire error log entry from both ends of the channels.

Do you have the appropriate LISTENERs running on each qmgr? Display listener status, and 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
View user's profile Send private message
ivanachukapawn
PostPosted: Thu Mar 17, 2016 6:37 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

I displayed listeners on both MQTT1 and TEST1 and they are both running listening on the correct ports. I disabled CHLAUTH on the queue managers and removed localaddr from all the channels. I restarted the queue managers and then discovered that I no longer can get a M071 connection (even after altering the admin channels for MCAUSER('mqm'). I'm getting host not available. Looked all over for why my M071 access no longer works for these 2 clustered qmgrs but could not discover the problem.
I thank you very much for the kind help on this problem (in short, the problem seems to be that despite configuring the cluster sender channels with a conname specifying IP and port, the connection attempt is being made with IP 127.0.0.1 and port 1414 (the wrong port)) - so I am going to blow away the queue managers and start over. Somehow I don't think I will see this problem again, but we shall see.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Mar 17, 2016 9:04 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

I'd suggest that you first attempt to create SDR-RCVR channels between the two qmgrs. Once those are successful, you can move on to cluster channels.
_________________
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
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 18, 2016 5:01 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

ivanachukapawn wrote:
I displayed listeners on both MQTT1 and TEST1 and they are both running listening on the correct ports. I disabled CHLAUTH on the queue managers and removed localaddr from all the channels. I restarted the queue managers and then discovered that I no longer can get a M071 connection (even after altering the admin channels for MCAUSER('mqm'). I'm getting host not available. Looked all over for why my M071 access no longer works for these 2 clustered qmgrs but could not discover the problem.
I thank you very much for the kind help on this problem (in short, the problem seems to be that despite configuring the cluster sender channels with a conname specifying IP and port, the connection attempt is being made with IP 127.0.0.1 and port 1414 (the wrong port)) - so I am going to blow away the queue managers and start over. Somehow I don't think I will see this problem again, but we shall see.

Probably because you're using MQ8 and forgot about CONAUTH?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ivanachukapawn
PostPosted: Fri Mar 18, 2016 5:06 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

fjb,

Naw, that's not it. I have CONAUTH taken care of with OPTIONAL set for both OS and LOCL. CHLAUTH is turned off - and I have an admin SVRCONN with MCAUSER set to mqm. I'm guessing whatever mysterious ghost is retrying my cluster senders is also emasculating my SVRCONN. I've made too many changes trying to find out what is wrong - so my plan is to start over fresh next week.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 18, 2016 5:25 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Make sure that whatever Firewall is running on the host machine is not messing up your connections too.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
bruce2359
PostPosted: Fri Mar 18, 2016 6:09 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9394
Location: US: west coast, almost. Otherwise, enroute.

ivanachukapawn wrote:
I've made too many changes trying to find out what is wrong - so my plan is to start over fresh next week.

In testing, tuning, and problem source identification, it is best practice to change only ONE thing at a time. And, begin with something that works successfully first.

Disable CONNAUTH and CHLAUTH.

Do basic connectivity testing first. Can you TCP ping? Telnet?

Then, get plain old SDR-RCVR channels to work successfully.
_________________
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
View user's profile Send private message
ivanachukapawn
PostPosted: Tue Mar 22, 2016 3:59 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

OK. I started over from scratch, attempting to follow excellent advice given by you guys (Bruce, FJB, Jeff and others).

I created 2 new qmgrs, LINEAR1 and LINEAR2
I disabled CONAUTH and CHLAUTH
I set admin SVRCONN LINEAR1.ADMIN and LINEAR2.ADMIN to MCAUSER('mqm')

I started the qmgrs and have good connectivity via the admin channels.

I created Sender and Receiver channels both ways between LINEAR1 and LINEAR2 and started these channels. They run OK.

I specified LINEAR1 and LINEAR2 as full repos for V8CLUSTER

I created cluster senders and receivers both ways between LINEAR1 and LINEAR2.



The short story is this (details later on):

LINEAR1:
display chstatus (*)
5 : display chstatus (*)
AMQ8417: Display Channel Status details.
CHANNEL(LINEAR2.TO.LINEAR1) CHLTYPE(RCVR)
CONNAME(10.55.175.65) CURRENT
RQMNAME(LINEAR2) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(LINEAR1.ADMIN) CHLTYPE(SVRCONN)
CONNAME(10.55.174.16) CURRENT
STATUS(RUNNING) SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(LIN1CLUS.TO.LIN2CLUS) CHLTYPE(CLUSSDR)
CONNAME(10.55.175.65(3122)) CURRENT
RQMNAME(LINEAR2) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)


LINEAR2:

display chstatus (*)
1 : display chstatus (*)
AMQ8417: Display Channel Status details.
CHANNEL(LINEAR2.TO.LINEAR1) CHLTYPE(SDR)
CONNAME(10.55.175.65(3121)) CURRENT
RQMNAME(LINEAR1) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(LINEAR1)
AMQ8417: Display Channel Status details.
CHANNEL(LINEAR2.ADMIN) CHLTYPE(SVRCONN)
CONNAME(10.55.174.16) CURRENT
STATUS(RUNNING) SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(LIN2CLUS.TO.LIN1CLUS) CHLTYPE(CLUSSDR)
CONNAME(127.0.0.1) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8417: Display Channel Status details.
CHANNEL(LIN1CLUS.TO.LIN2CLUS) CHLTYPE(CLUSRCVR)
CONNAME(10.55.175.65) CURRENT
RQMNAME(LINEAR1) STATUS(RUNNING)
SUBSTATE(RECEIVE)


In other words, I got the same problem as reported before - On LINEAR2 I have defined a CLUSTER SENDER :

display channel (LIN2CLUS.TO.LIN1CLUS)
3 : display channel (LIN2CLUS.TO.LIN1CLUS)
AMQ8414: Display Channel details.
CHANNEL(LIN2CLUS.TO.LIN1CLUS) CHLTYPE(CLUSSDR)
ALTDATE(2016-03-21) ALTTIME(12.44.15)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CLUSNL( ) CLUSTER(V8CLUSTER)
CLWLPRTY(0) CLWLRANK(0)
CLWLWGHT(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(10.55.175.65(3121))
CONVERT(NO) DESCR( )
DISCINT(6000) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(THREAD) MCAUSER( )
MODENAME( ) MONCHL(QMGR)
MSGDATA( ) MSGEXIT( )
NPMSPEED(FAST) PASSWORD( )
PROPCTL(COMPAT) RCVDATA( )
RCVEXIT( ) RESETSEQ(NO)
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCIPH( )
SSLPEER( ) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USEDLQ(YES) USERID( )

but this channel RETRIES because MQ ignores my connection IP(Port) and tries the connection with 127.0.0.1 and default 1414 -

just for the record: here are the listeners.

LINEAR2:

AMQ8630: Display listener information details.
LISTENER(TCP.3122) CONTROL(QMGR)
TRPTYPE(TCP) PORT(3122)
IPADDR( ) BACKLOG(0)
DESCR(Auto start/top TCP listener) ALTDATE(2016-03-21)
ALTTIME(10.44.47)

LINEAR1:

AMQ8630: Display listener information details.
LISTENER(TCP.3121) CONTROL(QMGR)
TRPTYPE(TCP) PORT(3121)
IPADDR( ) BACKLOG(0)
DESCR(Auto start/top TCP listener) ALTDATE(2016-03-21)
ALTTIME(10.42.36)


It looks to me like we have the same problem/question as before: Why does MQ ignore my specification of IP/Port on the cluster sender and try the connection instead with 127.0.0.1 1414 ?

and also for the record, here is the LINEAR2 error log relevant messages for the connection failure:

----- amqrccca.c : 1090 -------------------------------------------------------
03/22/2016 07:44:14 AM - Process(2251.17) User(mqm) Program(amqrmppa)
Host(localhost.localdomain) Installation(Installation1)
VRMF(8.0.0.4) QMgr(LINEAR2)

AMQ9002: Channel 'LIN2CLUS.TO.LIN1CLUS' is starting.

EXPLANATION:
Channel 'LIN2CLUS.TO.LIN1CLUS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
03/22/2016 07:44:14 AM - Process(2251.17) User(mqm) Program(amqrmppa)
Host(localhost.localdomain) Installation(Installation1)
VRMF(8.0.0.4) QMgr(LINEAR2)

AMQ9202: Remote host 'localhost (127.0.0.1) (1414)' not available, retry later.

EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'localhost
(127.0.0.1) (1414)' for channel LIN2CLUS.TO.LIN1CLUS 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
111 (X'6F'). 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
'localhost (127.0.0.1) (1414)' was not running. If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.
----- amqccita.c : 1209 -------------------------------------------------------
03/22/2016 07:44:14 AM - Process(2251.17) User(mqm) Program(amqrmppa)
Host(localhost.localdomain) Installation(Installation1)
VRMF(8.0.0.4) QMgr(LINEAR2)

AMQ9999: Channel 'LIN2CLUS.TO.LIN1CLUS' to host '127.0.0.1' ended abnormally.

EXPLANATION:
The channel program running under process ID 2251 for channel
'LIN2CLUS.TO.LIN1CLUS' ended abnormally. The host name is '127.0.0.1'; 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.
----- amqrccca.c : 1090 -------------------------------------------------------
mqm@localhost.localdomain(/var/mqm/qmgrs/LINEAR2/errors):
Back to top
View user's profile Send private message
exerk
PostPosted: Tue Mar 22, 2016 4:52 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

I see a definition for a CLUSSDR and CLUSRCVR for queue manager LINEAR2 but I only see a definition for a CLUSSDR in queue manager LINEAR1...
_________________
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
View user's profile Send private message
ivanachukapawn
PostPosted: Tue Mar 22, 2016 5:01 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

Starting MQSC for queue manager LINEAR1.


display channel (LIN2CLUS.TO.LIN1CLUS) ALL
1 : display channel (LIN2CLUS.TO.LIN1CLUS) ALL
AMQ8414: Display Channel details.
CHANNEL(LIN2CLUS.TO.LIN1CLUS) CHLTYPE(CLUSRCVR)
ALTDATE(2016-03-21) ALTTIME(12.44.57)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) CLUSNL( )
CLUSTER(V8CLUSTER) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME( ) CONVERT(NO)
DESCR( ) DISCINT(6000)
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)
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Mar 22, 2016 5:07 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

OK... You might want to revisit your cluster channel names...
but...
Can you show us the definition on LINEAR1 of channel
LINCLUS2.TO.LINCLUS1 ??

I would suggest following course of action:
  1. remove all cluster channel definitions
  2. On each qmgr start with defining the CLUSTER RECEIVER channel and make sure you have the CONNAME correctly defined as to pointing to itself.
    Use the TO.<QMNAME> convention. You should be able to verify that it is set up correctly by issuing dis clusqmgr(*) and see the correct definition for the queue manager you are working on.
    You might want to do demote to a PR and use refresh cluster repos(yes) to have a clean setup. Then reinstate them as FRs
  3. Finally define the cluster sender and point it to the other FR. Again you will have to use the TO.<OTHERFRNAME> convention to match the channel names.
  4. Start the sender channels
  5. Show the output of dis chs(to.*) for each of the queue managers.


Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ivanachukapawn
PostPosted: Tue Mar 22, 2016 6:01 am    Post subject: Reply with quote

Knight

Joined: 27 Oct 2003
Posts: 561

FJB,

I followed your recommended course of action (almost).

I deleted all sender/receiver/cluster sender/cluster receiver channels.

I updated FR on both queue managers to new cluster (CLUSTERMQ8)

On each queue manager I created cluster receiver first with conname IP/port pointing to itself.

On each queue manager I created cluster sender with conname IP/Port pointing to the other FR of course.

On LINEAR1:

dis chs (TO.*)
2 : dis chs (TO.*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.LINEAR2) CHLTYPE(CLUSSDR)
CONNAME(10.55.175.65(3122)) CURRENT
RQMNAME(LINEAR2) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
AMQ8417: Display Channel Status details.
CHANNEL(TO.LINEAR1) CHLTYPE(CLUSRCVR)
CONNAME(10.55.175.65) CURRENT
RQMNAME(LINEAR2) STATUS(RUNNING)
SUBSTATE(RECEIVE)


On LINEAR2:

dis chs (TO.*)
1 : dis chs (TO.*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.LINEAR2) CHLTYPE(CLUSRCVR)
CONNAME(10.55.175.65) CURRENT
RQMNAME(LINEAR1) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417: Display Channel Status details.
CHANNEL(TO.LINEAR1) CHLTYPE(CLUSSDR)
CONNAME(10.55.175.65(3121)) CURRENT
RQMNAME(LINEAR1) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)


So now MQ doesn't substitute 127.0.0.1 and port 1414 for the connection attempt - and all the channels are running OK.

Of the 2 substantive changes made to get this to work;

Used TO.[qmgrName] convention for cluster senders and receivers

Specified conname IP/Port on cluster receivers,

Which of these changes (or both) were responsible for getting these cluster channels running?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3  Next Page 2 of 3

MQSeries.net Forum Index » Clustering » RETRYING CLUSTER SENDERS dis chstatus shows wrong conname
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.