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 » CLUSSDR Retrying

Post new topic  Reply to topic
 CLUSSDR Retrying « View previous topic :: View next topic » 
Author Message
GheorgheDragos
PostPosted: Mon Dec 30, 2019 12:06 pm    Post subject: CLUSSDR Retrying Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Hello MQ community,

I am here asking for your help again with a situation I am facing with a cluster sender channel. I am running Kubuntu 19.10 with MQ9.1 on trial. There are 4 queue managers defined. MQA,MQB MQ1 and MQ2. For this instance, we will ignore MQ2 ( this I will later for exercising with overlapping clusters ). MQA and B are both full repositories. MQ1 is a partial repository.

Results of DIS CLUSQMGR(*) QMTYPE
from MQA
Code:
2019-12-30 20:41:46.090 MQA > dis clusqmgr(*) qmtype
     1 : dis clusqmgr(*) qmtype
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQ1)                           CHANNEL(MQ1.CL1)
   CLUSTER(CL1)                            QMTYPE(NORMAL)
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQB)                           CHANNEL(MQB.CL1)
   CLUSTER(CL1)                            QMTYPE(REPOS)
2019-12-30 20:41:51.270 MQA >


from MQB
2019-12-30 20:57:49.641 MQB > dis clusqmgr(*) qmtype
     1 : dis clusqmgr(*) qmtype
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQB)                           CHANNEL(MQB.CL1)
   CLUSTER(CL1)                            QMTYPE(REPOS)
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(SYSTEM.TEMPQMGR.192.168.1.15(1416))
   CHANNEL(MQA.CL1)                        CLUSTER(CL1)
   QMTYPE(REPOS)                       
2019-12-30 20:57:54.381 MQB >

Notice how MQA is displayed ?

The CLUSSDR and RCVR channels are defined as such ( focusing only on MQA and B )

MQA
2019-12-30 20:59:08.972 MQA > dis chl(mq*) conname
     3 : dis chl(mq*) conname
AMQ8414I: Display Channel details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSRCVR)
   CONNAME( )                           
AMQ8414I: Display Channel details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSSDR)
   CONNAME(192.168.1.15(1417))         
2019-12-30 20:59:19.229 MQA >

MQB
2019-12-30 20:59:37.714 MQB > dis chl(mq*) conname
     1 : dis chl(mq*) conname
AMQ8414I: Display Channel details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSSDR)
   CONNAME(192.168.1.15(1416))         
AMQ8414I: Display Channel details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSRCVR)
   CONNAME( )                           
2019-12-30 20:59:44.237 MQB >


The CLUSSDR from MQB to MQA is working
2019-12-30 20:59:44.237 MQB > dis chstatus(*)
     2 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSSDR)
   CONNAME(192.168.1.15(1416))             CURRENT
   RQMNAME(MQA)                            STATUS(RUNNING)
   SUBSTATE(MQGET)                         XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
2019-12-30 21:00:31.964 MQB >


from MQA to MQB... retrying
2019-12-30 21:00:58.801 MQA > dis chstatus(*)
     1 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSRCVR)
   CONNAME(192.168.1.15)                   CURRENT
   RQMNAME(MQB)                            STATUS(RUNNING)
   SUBSTATE(RECEIVE)                   
AMQ8417I: Display Channel Status details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSSDR)
   CONNAME(127.0.1.1)                      CURRENT
   RQMNAME( )                              STATUS(RETRYING)
   SUBSTATE( )                             XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
2019-12-30 21:01:02.900 MQA >


Why is the conname switched to 127.0.0.1 ??? probably this is the reason. I cannot find out why. I have deleted and redefined the MQB.CL1 CLUSSDR channel. I have altered the channel to readd the correct conname. In MQExplorer, right clicking on MQA, selecting properties, navigating to CLUSTER I see the field that says - THIS QUEUE MANAGER IS A MEMBER OF THESE CLUSTERS - nothing there??? on MQB I see this entry plus full repository = yes. For realism purposes, I do not wish to delete/define the queue manager but try to solve it. Another curious thing is that on MQExplorer, in the channels tab of MQA, the conname is correctly set to 192.168.1.15(1417) . Nothing in the AMQER*.LOG.. except I am being spammed with :

Code:
----- amqxufnx.c : 2390 -------------------------------------------------------
30.12.2019 21:05:35 - Process(5258.3) User(dragos) Program(runmqsc)
                    Host(dragos-OptiPlex-7010) Installation(Installation1)
                    VRMF(9.1.0.0)
                    Time(2019-12-30T20:05:35.079Z)
                    ArithInsert1(536895861)
                    CommentInsert1(/opt/mqm/lib64/libedit.so)
                    CommentInsert2(libncurses.so.5: cannot open shared object file: No such file or directory)
                    CommentInsert3(64)

AMQ6175E: The system could not dynamically load the shared library
'/opt/mqm/lib64/libedit.so'. The system returned error message
'libncurses.so.5: cannot open shared object file: No such file or directory'.

EXPLANATION:
This message applies to UNIX systems. The shared library
'/opt/mqm/lib64/libedit.so' failed to load correctly due to a problem with the
library.
ACTION:
Check the file access permissions and that the file has not been corrupted.
----- amqxufnx.c : 1436 -------------------------------------------------------


The /etc/services file contains :

MQ1 1414/tcp
MQ2 1415/tcp
MQA 1416/tcp
MQB 1417/tcp

Moreover, are there any linux people here who know when I am inside RUNMQSC why i cannot use the up/down arrows to rerieve commands, and instead I get this ?
Code:

2019-12-30 21:05:35.079 MQA > ^[[A^[[C^[[A^[[D^[[B^[[D^[[C^[[A^[[D^[[B^[[C^[[D

Also, is it possible to add a functionality to this forum entry box where we can select Courier New font for example for aligning ?

Any input would be greatly appreciated.

Dragos Gheorghe
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Dec 30, 2019 1:36 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Before you defined any CLUSSDR from the Partial Repositories (PRs) to the Full Repositories (FRs) did you ensure that both FRs were properly communicating, i.e. that the CLUSSDR/CLUSRCVR to/from each were in RUNNING state?

IP Address 127.0.1.1 is the 'loop-back' address, and all your queue managers are on the same box (presumably, going by the IP Address in each displayed object) so I would expect to see this, or 127.0.0.1 if there is a problem.

I suggest shutting down the PRs until you can resolve the FR issue, and if you would kindly post the object definitions for the FR CLUSSDR/CLUSRCVR objects I'd be obliged, thank you.
_________________
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
GheorgheDragos
PostPosted: Mon Dec 30, 2019 11:36 pm    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Hello,

Hmmm, I am not 100% sure but am confident that the SDR/RCVR cluster connections were up and running before I decided to add MQ1 ( PR ) . I would always make sure that what I did is correct before moving on to the next step. I have just removed MQ1 from the cluster ( ALTER QMGR REPOS(' '), delete the RCVR and SDR cluster channels, and performed a cluster reset on MQA with action(force remove) ) and now, DIS CLUSMQGR(*) on MQA shows the display without MQ1

Code:
2019-12-31 08:27:56.782 MQA > dis clusqmgr(*)
     1 : dis clusqmgr(*)
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQB)                           CHANNEL(MQB.CL1)
   CLUSTER(CL1)                         
2019-12-31 08:27:59.732 MQA >

Here are the definitions aske. All of them indeed point to a local IP on the same machine, since, well, all are hosted on one, with different ports of course.

MQA
2019-12-31 08:27:59.732 MQA > dis chl(mqa.cl1)
     2 : dis chl(mqa.cl1)
AMQ8414I: Display Channel details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSRCVR)
   ALTDATE(2019-12-30)                     ALTTIME(13.24.45)
   BATCHHB(0)                              BATCHINT(0)
   BATCHLIM(5000)                          BATCHSZ(50)
   CERTLABL( )                             CLUSNL( )
   CLUSTER( )                              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)
2019-12-31 08:29:35.242 MQA >



2019-12-31 08:30:47.731 MQA > dis chl(mqb*) all
     4 : dis chl(mqb*) all
AMQ8414I: Display Channel details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSSDR)
   ALTDATE(2019-12-30)                     ALTTIME(20.07.46)
   BATCHHB(0)                              BATCHINT(0)
   BATCHLIM(5000)                          BATCHSZ(50)
   CLUSNL( )                               CLUSTER(CL1)
   CLWLPRTY(0)                             CLWLRANK(0)
   CLWLWGHT(50)                            COMPHDR(NONE)
   COMPMSG(NONE)                           CONNAME(192.168.1.15(1417))
   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( )
2019-12-31 08:30:57.093 MQA >

MQB
2019-12-31 08:31:57.490 MQB > dis chl(mqa*) all
     1 : dis chl(mqa*) all
AMQ8414I: Display Channel details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSSDR)
   ALTDATE(2019-12-30)                     ALTTIME(13.28.37)
   BATCHHB(0)                              BATCHINT(0)
   BATCHLIM(5000)                          BATCHSZ(50)
   CLUSNL( )                               CLUSTER(CL1)
   CLWLPRTY(0)                             CLWLRANK(0)
   CLWLWGHT(50)                            COMPHDR(NONE)
   COMPMSG(NONE)                           CONNAME(192.168.1.15(1416))
   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( )
2019-12-31 08:32:03.169 MQB >


2019-12-31 08:32:29.028 MQB > dis chl(mqb*) all
     5 : dis chl(mqb*) all
AMQ8414I: Display Channel details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSRCVR)
   ALTDATE(2019-12-30)                     ALTTIME(13.28.01)
   BATCHHB(0)                              BATCHINT(0)
   BATCHLIM(5000)                          BATCHSZ(50)
   CERTLABL( )                             CLUSNL( )
   CLUSTER(CL1)                            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)
2019-12-31 08:33:00.123 MQB >


CLUSSDR MQB.CL1 and CLUSRCVR MQB.CL1 both exist. Conname is correct. MQ1 PR has been removed ( not just terminated ) from the cluster, yet MQA seems to be sick.

2019-12-31 08:33:00.123 MQB > dis clusqmgr(*) qmtype
     6 : dis clusqmgr(*) qmtype
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQB)                           CHANNEL(MQB.CL1)
   CLUSTER(CL1)                            QMTYPE(REPOS)
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(SYSTEM.TEMPQMGR.192.168.1.15(1416))
   CHANNEL(MQA.CL1)                        CLUSTER(CL1)
   QMTYPE(REPOS)                       
2019-12-31 08:34:38.858 MQB >

I will check now to see whether the trial version has limitation on some functionalities.

2019-12-31 08:35:13.968 MQA > dis clusqmgr(*) qmtype
     1 : dis clusqmgr(*) qmtype
AMQ8441I: Display Cluster Queue Manager details.
   CLUSQMGR(MQB)                           CHANNEL(MQB.CL1)
   CLUSTER(CL1)                            QMTYPE(REPOS)
2019-12-31 08:35:18.156 MQA >

2019-12-31 08:38:16.186 MQA > dis chstatus(*)
     3 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
   CHANNEL(MQB.CL1)                        CHLTYPE(CLUSSDR)
   CONNAME(127.0.1.1)                      CURRENT
   RQMNAME( )                              STATUS(RETRYING)
   SUBSTATE( )                             XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
2019-12-31 08:38:19.437 MQA >




Dragos Gheorghe

PS: Any idea about why I can't retrieve commands from RUNMQSC with directional arrows ?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Dec 31, 2019 6:17 am    Post subject: Reply with quote

Grand High Poobah

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

You problem is that you say QMA is a repository but neither CLUSTER nor CLUSNL have a value on the cluster receiver channel!!!

This is why on QMA, QMA does not show in the clusterqmgr(*) list.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
exerk
PostPosted: Tue Dec 31, 2019 6:50 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

fjb_saper wrote:
You problem is that you say QMA is a repository but neither CLUSTER nor CLUSNL have a value on the cluster receiver channel!!!...

Hence why I asked for the definitions to be posted and not the output of display - that would probably have caused a re-read of the definitions and the spot of the missing attribute
_________________
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
GheorgheDragos
PostPosted: Wed Jan 01, 2020 1:34 am    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Hello, and Happy New Year! May 2020 bring you personal and professional accomplishments. Back to topic. I have just checked ( with a agitated baby next to me so I may make some typos ), and the only channel that was not defined as part of the cluster was on MQA the receiver from MQB ( corrected now ). And even then the channel was started. Below screenshots of the overview from MQExplorer.

[img]
https://ibb.co/2ydkjKS
[/img]
[img]
https://ibb.co/PC2WTrG
[/img]
[img]
https://ibb.co/cQ6LL12
[/img]
[img]
https://ibb.co/28Vq4sY
[/img]


You have asked for the definition and not the status of the channels. Here they are. As yo can see, all are part of the CL1 cluster.
output from MQA

2020-01-01 10:31:24.774 MQA > dis chl(mq*) all
1 : dis chl(mq*) all
AMQ8414I: Display Channel details.
CHANNEL(MQA.CL1) CHLTYPE(CLUSRCVR)
ALTDATE(2020-01-01) ALTTIME(10.15.14)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) CLUSNL( )
CLUSTER(CL1) 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)
AMQ8414I: Display Channel details.
CHANNEL(MQB.CL1) CHLTYPE(CLUSSDR)
ALTDATE(2019-12-30) ALTTIME(20.07.46)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CLUSNL( ) CLUSTER(CL1)
CLWLPRTY(0) CLWLRANK(0)
CLWLWGHT(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(192.168.1.15(1417))
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( )
2020-01-01 10:31:38.317 MQA >


Output from MQB

2020-01-01 10:32:35.606 MQB > dis chl(mq*) all
1 : dis chl(mq*) all
AMQ8414I: Display Channel details.
CHANNEL(MQA.CL1) CHLTYPE(CLUSSDR)
ALTDATE(2019-12-30) ALTTIME(13.28.37)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CLUSNL( ) CLUSTER(CL1)
CLWLPRTY(0) CLWLRANK(0)
CLWLWGHT(50) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(192.168.1.15(1416))
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( )
AMQ8414I: Display Channel details.
CHANNEL(MQB.CL1) CHLTYPE(CLUSRCVR)
ALTDATE(2019-12-30) ALTTIME(13.28.01)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) CLUSNL( )
CLUSTER(CL1) 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)
2020-01-01 10:32:40.172 MQB >


DIS CHSTATUS(*) from MQA

2020-01-01 10:33:07.877 MQA > dis chstatus(*)
1 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
CHANNEL(MQA.CL1) CHLTYPE(CLUSRCVR)
CONNAME(192.168.1.15) CURRENT
RQMNAME(MQB) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417I: Display Channel Status details.
CHANNEL(MQB.CL1) CHLTYPE(CLUSSDR)
CONNAME(127.0.1.1) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
2020-01-01 10:33:10.700 MQA >


Again the IP address is changed to the loopback.

CHSTATUS(*) from MQB

2020-01-01 10:32:55.051 MQB > dis chstatus(*)
3 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
CHANNEL(MQA.CL1) CHLTYPE(CLUSSDR)
CONNAME(192.168.1.15(1416)) CURRENT
RQMNAME(MQA) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)


I have issued a REFRESH CLUSTER(CL1) on both queue managers, checked. Still a problem. Restarted both of them. Still a problem. I do not know why the [img] etc doesn't work, at least for me, I see the HTML is off even I turned it on in profile..

Dragos
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Jan 01, 2020 3:27 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

GheorgheDragos wrote:
...You have asked for the definition and not the status of the channels. Here they are...

And again you have posted the DISPLAY of the channels, not the DEFINITIONS! They are two different animals.

The reason I asked for the definitions is because it is generally easier to spot typos etc. in those than to pick out problems from the 'clutter' of a display command, especially as most attributes are left default/initial value, e.g.

Quote:
DEFINE CHANNEL('CL01.SSL.CQM1') +
CHLTYPE(CLUSRCVR) +
CLUSTER('CL01') +
CONNAME('localhost(1415)') +
SSLCIPH('TLS_RSA_WITH_AES_128_CBC_SHA256') +
TRPTYPE(TCP) +
REPLACE

DEFINE CHANNEL('CL01.SSL.CQM2') +
CHLTYPE(CLUSSDR) +
CLUSTER('CLO1') +
CONNAME('localhost(1416)') +
SSLCIPH('TLS_RSA_WITH_AES_128_CBC_SHA256') +
TRPTYPE(TCP) +
REPLACE


There is a deliberate error in one of those definitions...
_________________
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
GheorgheDragos
PostPosted: Wed Jan 01, 2020 9:53 am    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Hello,

I did not define the channels like that. I simply used "define chl(mb* ... in runmqsc. I have no formatted definition file. In my work we use them ( on z/OS ) but not at home for testing purposes. I will now delete and define the channels again, but as you can see, in all that clutter indeed, is that both exist in the same cluster and ip address + port are correct. After delete/define, same issue, retrying and nothing in AMQERR01.LOG.

Dragos
Back to top
View user's profile Send private message
hughson
PostPosted: Wed Jan 01, 2020 12:51 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand

GheorgheDragos wrote:
Code:
MQA
2019-12-31 08:27:59.732 MQA > dis chl(mqa.cl1)
     2 : dis chl(mqa.cl1)
AMQ8414I: Display Channel details.
   CHANNEL(MQA.CL1)                        CHLTYPE(CLUSRCVR)
   ALTDATE(2019-12-30)                     ALTTIME(13.24.45)
   BATCHHB(0)                              BATCHINT(0)
   BATCHLIM(5000)                          BATCHSZ(50)
   CERTLABL( )                             CLUSNL( )
   CLUSTER( )                              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)


I am curious, could you say why this CLUSRCVR channel has a blank CONNAME? Normally a CLUSRCVR will contain the CONNAME to be used for automatically created CLUSSDR channels to use to connect to it. This is an important part of setting up a cluster. A CLUSRCVR has two roles in life; one, to be a RCVR channel, and two, to be a template for the creation of CLUSSDRs. This channel definition appears to only be set up for one.

I see your MQB.CL1 CLUSRCVR is the same.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
GheorgheDragos
PostPosted: Wed Jan 01, 2020 1:23 pm    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Everything I have done so far has been done using this link : https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/q017360_.htm
It is impossible for me to recreate the situation, because I have done this on MQA + MQB ( which in my scenario should be the full repositories for cluster CL1)

* deleted all cluster sdr/rcvr channels
* alter qmgr cluster(' ') repos(no)
* reset cluster(cl1) action(forceremove) qmname(mqa/b) queues(yes) - this was done on both queue managers, but on MQA it just doesn't go away, after stop restart etc :

Quote:
2020-01-01 22:16:56.180 MQA > dis clusqmgr(*) all
1 : dis clusqmgr(*) all
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(MQB) ALTDATE(2020-01-01)
ALTTIME(18.51.03) BATCHHB(0)
BATCHINT(0) BATCHLIM(5000)
BATCHSZ(50) CHANNEL(MQB.CL1)
CLUSDATE(2020-01-01) CLUSTER(CL1)
CLUSTIME(18.51.03) CLWLPRTY(0)
CLWLRANK(0) CLWLWGHT(50)
COMPHDR(NONE) COMPMSG(NONE)
CONNAME(127.0.1.1) CONVERT(NO)
DEFTYPE(CLUSSDRA) DESCR( )
DISCINT(6000) HBINT(300)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(THREAD) MCAUSER( )
MODENAME( ) MRDATA( )
MREXIT( ) MRRTY(10)
MRTMR(1000) MSGDATA( )
MSGEXIT( ) NETPRTY(0)
NPMSPEED(FAST) PASSWORD( )
PROPCTL(COMPAT) PUTAUT(DEF)
QMID(MQB_2019-12-30_12.47.30) QMTYPE(REPOS)
RCVDATA( ) RCVEXIT( )
SCYDATA( ) SCYEXIT( )
SENDDATA( ) SENDEXIT( )
SEQWRAP(999999999) SHORTRTY(10)
SHORTTMR(60) SSLCAUTH(REQUIRED)
SSLCIPH( ) SSLPEER( )
STATUS(RETRYING) SUSPEND(NO)
TPNAME( ) TRPTYPE(TCP)
USEDLQ(YES) USERID( )
VERSION(09010000) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
2020-01-01 22:17:00.320 MQA >


in MQExplorer, XMITQ SYSTEM.CLUSTER.TRANSMIT.QUEUE had 7 messages in it. I cleared them. Still the same, MQA refuses to let go of cluster CL1. After doing some reading ( https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.tro.doc/q039160_.htm ) I did this display :

Quote:

MQA
1 : dis clusqmgr(*) conname
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(MQA) CHANNEL(MQA.CL1)
CLUSTER(CL1) CONNAME(127.0.1.1)
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(MQB) CHANNEL(MQB.CL1)
CLUSTER(CL1) CONNAME(127.0.1.1)


MQB

1 : dis clusqmgr(*) conname
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(MQB) CHANNEL(MQB.CL1)
CLUSTER(CL1) CONNAME(127.0.1.1)
AMQ8441I: Display Cluster Queue Manager details.
CLUSQMGR(SYSTEM.TEMPQMGR.192.168.1.15(1416))
CHANNEL(MQA.CL1) CLUSTER(CL1)
CONNAME(192.168.1.15(1416))


After noticing that somehow both queue managers are attracted to the loopback ip, i modified the MQB.CL1 sender channel with this IP address and port 1417 of MQB, and restarted it. So in MQExplorer properties panel the ip was 127.0.0.1 and in DIS CHSTATUS(*) the IP was :

Quote:
2020-01-01 21:53:35.421 MQA > dis chstatus(*)
10 : dis chstatus(*)
AMQ8417I: Display Channel Status details.
CHANNEL(MQA.CL1) CHLTYPE(CLUSRCVR)
CONNAME(192.168.1.15) CURRENT
RQMNAME(MQB) STATUS(RUNNING)
SUBSTATE(RECEIVE)
AMQ8417I: Display Channel Status details.
CHANNEL(MQB.CL1) CHLTYPE(CLUSSDR)
CONNAME(127.0.1.1) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)


From where 127.0.1.1 ?????? and Why is MQ Explorer not telling the truth. And why is MQA still showing output from MQB clusqmgr and status as retrying. I cannot delete and start over because in real life I simply cannot afford to do such.

Dragos Gheorghe
Back to top
View user's profile Send private message
GheorgheDragos
PostPosted: Wed Jan 01, 2020 2:13 pm    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

The problem appeared to have been this channel was still in retrying status, I do not know how because it was deleted and one cannot delete a channel while it is in use. Or maybe retrying satus is accepable.. anyhow, it appears that this retrying status persisted after restart. After I stopped the channel, and restarted the queue manager, the clusqmgr(*) all shows now nothing.

The situation has been fixed... I feel a bit silly, after I defined a new set of clusrcvr channels, and one cluster sender from MQA to MQB, MQB to MQA CLUSSDR has been auto defined and channel is up and running I realize that maybe a pair of CLUSSDR-RCVR was not a smart move to to, and while one pair was working, the second pair started to complain.
Back to top
View user's profile Send private message
hughson
PostPosted: Thu Jan 02, 2020 12:37 am    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand

GheorgheDragos wrote:
From where 127.0.1.1 ??????

I suspect it is as a result of having a CLUSRCVR with a CONNAME that is blank. Do you know why your CLUSRCVR channels did not have a CONNAME - was that deliberate? Omitting the CONNAME tells the queue manager to generate a CONNAME from the IP address of the machine - a handy feature for when you have a machine with a DHCP address.

A CLUSRCVR needs a CONNAME - you cannot have a working cluster without one.

I suspect your blank CONNAMEs on your two CLUSRCVRs to be the root cause.

Please set up your cluster with properly filled in CONNAME fields to see if you have the problem now.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
GheorgheDragos
PostPosted: Sat Jan 04, 2020 5:37 am    Post subject: Reply with quote

Acolyte

Joined: 28 Jun 2018
Posts: 51

Hello, please forgive the very late answer. Indeed, when the conname on the CLSRCVR channels specified the host QMGRs hostname and port, the cluster magically started to work ( including the PR added afterwards ).
Many thanks for your continuous patience and support in helping me in this endeavor.

Dragos Gheorghe
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Jan 04, 2020 6:12 am    Post subject: Reply with quote

Poobah

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

Neither magic nor luck.

To be functional, a CLUSRCVR channel definition must provide complete and accurate information such that other qmgrs that are members of the same cluster can successfully create CSUSSDR channels back to your qmgr - based on the CLUSRCVR definition you provided.
_________________
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
hughson
PostPosted: Sat Jan 04, 2020 3:03 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand

Glad to hear all is working now.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » CLUSSDR Retrying
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.