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 » IBM MQ Installation/Configuration Support » Windows Configuration

Post new topic  Reply to topic Goto page 1, 2  Next
 Windows Configuration « View previous topic :: View next topic » 
Author Message
Andrew.Potter
PostPosted: Mon Jul 18, 2016 2:52 pm    Post subject: Windows Configuration Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

Hi all,

I am having issues with some MQ channels and can not seem to get my head around what is actually happening.

We have a couple of channels that operate over wireless connections. When the wireless connection
is dropped for whatever reason the channels do not always reconnect/restart seamlessly.

A subset of the current configuration is that we have a main server running a queue manager.
That queue manager has a number of channels. Then we have four (4) cranes running their own queue managers
and appropriate channels. Two of the cranes seem to be operating quite well, the channels do drop out due
to wireless issues but the channels seem to repair themselves. whereas two other cranes seem to need manual
intervention at times to repair the channel connections.

I have run the DISPLAY CHANNEL ALL information for each of the cranes these configurations are listed below,

I have read through the "Keeping Channels Up and Running" IBM document but cannot see an answer there. I do not profess to understanding it completely though.

The only difference is in the heartbeat. I changed this from 5 to 60 on the crane side to try and avoid the cache and resources being flushed too often, I am sure I read that somewhere on this forum. It was originally the same as crane 5 (set at 5), but we send a loopback message that is targeted for every 5 seconds. I believe changing the heartbeat to 60 seconds should have helped more than hindered, but maybe i am wrong.

I do realise that on channel start up MQ will negotiate and use the 60 second heartbeat from the crane rather than the 5 from the server side, as it is longer.

We do not have any TCP keepalive settings changed, all are at the defaults.

We do have a second development set of computers that we can test with
but the cranes are hardwired not wireless. I have tried AdoptNewMCA but it did not seem to help. Tests were conducted by having the channels up and
running, then pulling the network cable out until the channels went into retrying mode. Then replacing the network cable.

Any ideas where I should be devoting my time?
Do you see any obvious configuration issues?

Can anybody explain why the server side port numbers are different to the crane side port numbers, even on the working crane?


Thanks for your time and help
Andrew Potter

Configuration settings in next post.
Back to top
View user's profile Send private message
Andrew.Potter
PostPosted: Mon Jul 18, 2016 2:54 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

First the crane that works.

Crane side Config (MQSeries V5.3)

Used
display channel(CRANE5.TO.HCPDCMS) all
display channel(HCPDCMS.TO.CRANE5) all
dis ql(HCPDCMS.XMIT.QUEUE)

Result
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager CRANE5.

Code:

       :
     1 : display channel(CRANE5.TO.HCPDCMS) all
AMQ8414: Display Channel details.
   CHANNEL(CRANE5.TO.HCPDCMS)              CHLTYPE(SVR)
   TRPTYPE(TCP)                            DESCR(Sending Channel to HCPDCMS)
   XMITQ(HCPDCMS.XMIT.QUEUE)               MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(7200)                          SHORTTMR(2)
   LONGRTY(999999999)                      LONGTMR(20)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        CONVERT(NO)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlhcpdwol-csprodap1.stlwol.bsl.net(1415))
   HBINT(5)                                BATCHINT(0)
   NPMSPEED(FAST)                          SSLCIPH( )
   SSLCAUTH(REQUIRED)                      BATCHHB(0)
   LOCLADDR( )                             KAINT(AUTO)
   MCAUSER( )                              ALTDATE(2012-07-09)
   ALTTIME(19.45.09)                       SSLPEER()
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
       :
     2 : display channel(HCPDCMS.TO.CRANE5) all
AMQ8414: Display Channel details.
   CHANNEL(HCPDCMS.TO.CRANE5)              CHLTYPE(RQSTR)
   TRPTYPE(TCP)                         
   DESCR(Channel for receiving from HCPDCMS)
   MCANAME( )                              MODENAME( )
   TPNAME( )                               BATCHSZ(50)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        PUTAUT(DEF)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlhcpdwol-csprodap1.stlwol.bsl.net(1415))
   MREXIT( )                               MRDATA( )
   MRRTY(50)                               MRTMR(1000)
   HBINT(5)                                NPMSPEED(FAST)
   SSLCIPH( )                              SSLCAUTH(REQUIRED)
   LOCLADDR( )                             KAINT(AUTO)
   MCAUSER( )                              ALTDATE(2012-07-09)
   ALTTIME(19.49.35)                       SSLPEER()
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
       :
     3 : dis ql(HCPDCMS.XMIT.QUEUE)
AMQ8409: Display Queue details.
   DESCR(Queue for transporting messages to HCPDCMS)
   PROCESS( )                              BOQNAME( )
   INITQ(SYSTEM.CHANNEL.INITQ)             TRIGDATA(CRANE5.TO.HCPDCMS)
   CLUSTER( )                              CLUSNL( )
   QUEUE(HCPDCMS.XMIT.QUEUE)               CRDATE(2009-11-23)
   CRTIME(10.05.00)                        ALTDATE(2016-07-14)
   ALTTIME(10.55.47)                       GET(ENABLED)
   PUT(ENABLED)                            DEFPRTY(0)
   DEFPSIST(YES)                           MAXDEPTH(5000)
   MAXMSGL(4194304)                        BOTHRESH(0)
   SHARE                                   DEFSOPT(SHARED)
   HARDENBO                                MSGDLVSQ(PRIORITY)
   RETINTVL(999999999)                     USAGE(XMITQ)
   TRIGGER                                 TRIGTYPE(FIRST)
   TRIGDPTH(1)                             TRIGMPRI(0)
   QDEPTHHI(80)                            QDEPTHLO(20)
   QDPMAXEV(ENABLED)                       QDPHIEV(DISABLED)
   QDPLOEV(DISABLED)                       QSVCINT(999999999)
   QSVCIEV(NONE)                           DISTL(YES)
   NPMCLASS(NORMAL)                        DEFTYPE(PREDEFINED)
   TYPE(QLOCAL)                            SCOPE(QMGR)
   DEFBIND(OPEN)                           IPPROCS(1)
   OPPROCS(2)                              CURDEPTH(0)
3 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.

From crane that is not working/ restarting automatically
Used
display channel(CRANE2.TO.HCPDCMS) all
display channel(HCPDCMS.TO.CRANE2) all
dis ql(HCPDCMS.XMIT.QUEUE)
Code:

Result
5724-B41 (C) Copyright IBM Corp. 1994, 2002.  ALL RIGHTS RESERVED.

Starting MQSC for queue manager CRANE2.
       :
     1 : display channel(CRANE2.TO.HCPDCMS) all
AMQ8414: Display Channel details.
   CHANNEL(CRANE2.TO.HCPDCMS)              CHLTYPE(SVR)
   TRPTYPE(TCP)                            DESCR(Sending Channel to HCPDCMS)
   XMITQ(HCPDCMS.XMIT.QUEUE)               MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(7200)                          SHORTTMR(2)
   LONGRTY(999999999)                      LONGTMR(20)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        CONVERT(NO)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlhcpdwol-csprodap1.stlwol.bsl.net(1415))
   HBINT(60)                               BATCHINT(0)
   NPMSPEED(FAST)                          SSLCIPH( )
   SSLCAUTH(REQUIRED)                      BATCHHB(0)
   LOCLADDR( )                             KAINT(AUTO)
   MCAUSER( )                              ALTDATE(2016-07-07)
   ALTTIME(10.37.02)                       SSLPEER()
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
       :
     2 : display channel(HCPDCMS.TO.CRANE2) all
AMQ8414: Display Channel details.
   CHANNEL(HCPDCMS.TO.CRANE2)              CHLTYPE(RQSTR)
   TRPTYPE(TCP)                         
   DESCR(Channel for receiving from HCPDCMS)
   MCANAME( )                              MODENAME( )
   TPNAME( )                               BATCHSZ(50)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        PUTAUT(DEF)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlhcpdwol-csprodap1.stlwol.bsl.net(1415))
   MREXIT( )                               MRDATA( )
   MRRTY(50)                               MRTMR(1000)
   HBINT(60)                               NPMSPEED(FAST)
   SSLCIPH( )                              SSLCAUTH(REQUIRED)
   LOCLADDR( )                             KAINT(AUTO)
   MCAUSER( )                              ALTDATE(2016-07-07)
   ALTTIME(10.35.55)                       SSLPEER()
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
       :
     3 : dis ql(HCPDCMS.XMIT.QUEUE)
AMQ8409: Display Queue details.
   DESCR(Queue for transporting messages to HCPDCMS)
   PROCESS( )                              BOQNAME( )
   INITQ(SYSTEM.CHANNEL.INITQ)             TRIGDATA(CRANE2.TO.HCPDCMS)
   CLUSTER( )                              CLUSNL( )
   QUEUE(HCPDCMS.XMIT.QUEUE)               CRDATE(2016-05-05)
   CRTIME(12.45.05)                        ALTDATE(2016-07-19)
   ALTTIME(05.52.17)                       GET(ENABLED)
   PUT(ENABLED)                            DEFPRTY(0)
   DEFPSIST(YES)                           MAXDEPTH(5000)
   MAXMSGL(4194304)                        BOTHRESH(0)
   SHARE                                   DEFSOPT(SHARED)
   HARDENBO                                MSGDLVSQ(PRIORITY)
   RETINTVL(999999999)                     USAGE(XMITQ)
   TRIGGER                                 TRIGTYPE(FIRST)
   TRIGDPTH(1)                             TRIGMPRI(0)
   QDEPTHHI(80)                            QDEPTHLO(20)
   QDPMAXEV(ENABLED)                       QDPHIEV(DISABLED)
   QDPLOEV(DISABLED)                       QSVCINT(999999999)
   QSVCIEV(NONE)                           DISTL(YES)
   NPMCLASS(NORMAL)                        DEFTYPE(PREDEFINED)
   TYPE(QLOCAL)                            SCOPE(QMGR)
   DEFBIND(OPEN)                           IPPROCS(1)
   OPPROCS(2)                              CURDEPTH(0)
3 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.


Server side Config (MQSeries V5.3)

First the one that seems to behave better

Used
display channel(CRANE5.TO.HCPDCMS) all
display channel(HCPDCMS.TO.CRANE5) all
dis ql(HCPDCMS.XMIT.QUEUE)
Code:

Result
5724-B41 (C) Copyright IBM Corp. 1994, 2002.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager HCPDCMS.

    1 : display channel(CRANE5.TO.HCPDCMS) all
AMQ8414: Display Channel details.
   CHANNEL(CRANE5.TO.HCPDCMS)              CHLTYPE(RQSTR)
   TRPTYPE(TCP)                            DESCR(Inbound channel from CRANE5)
   MCANAME( )                              MODENAME( )
   TPNAME( )                               BATCHSZ(50)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        PUTAUT(DEF)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlwol-hcpdcrn5(1414))          MREXIT( )
   MRDATA( )                               MRRTY(10)
   MRTMR(1000)                             HBINT(5)
   NPMSPEED(FAST)                          SSLCIPH( )
   SSLCAUTH(REQUIRED)                      LOCLADDR( )
   KAINT(AUTO)                             MCAUSER( )
   ALTDATE(2009-04-16)                     ALTTIME(16.28.28)
   SSLPEER()                           
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
    2 : display channel(HCPDCMS.TO.CRANE5) all
AMQ8414: Display Channel details.
   CHANNEL(HCPDCMS.TO.CRANE5)              CHLTYPE(SVR)
   TRPTYPE(TCP)                            DESCR(Outbound channel to CRANE5)
   XMITQ(CRANE5.XMIT.QUEUE)                MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(7200)                          SHORTTMR(5)
   LONGRTY(999999999)                      LONGTMR(20)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        CONVERT(NO)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlwol-hcpdcrn5(1414))          HBINT(5)
   BATCHINT(0)                             NPMSPEED(FAST)
   SSLCIPH( )                              SSLCAUTH(REQUIRED)
   BATCHHB(0)                              LOCLADDR( )
   KAINT(AUTO)                             MCAUSER( )
   ALTDATE(2016-07-06)                     ALTTIME(15.22.51)
   SSLPEER()                           
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
    3 : display ql(CRANE5.XMIT.QUEUE)
AMQ8409: Display Queue details.
   DESCR(Transmit Queue to CRANE5)         PROCESS( )
   BOQNAME( )                              INITQ(SYSTEM.CHANNEL.INITQ)
   TRIGDATA(HCPDCMS.TO.CRANE5)             CLUSTER( )
   CLUSNL( )                               QUEUE(CRANE5.XMIT.QUEUE)
   CRDATE(2009-03-31)                      CRTIME(12.37.39)
   ALTDATE(2016-07-18)                     ALTTIME(02.11.43)
   GET(ENABLED)                            PUT(ENABLED)
   DEFPRTY(5)                              DEFPSIST(YES)
   MAXDEPTH(5000)                          MAXMSGL(4194304)
   BOTHRESH(0)                             SHARE
   DEFSOPT(EXCL)                           HARDENBO
   MSGDLVSQ(FIFO)                          RETINTVL(999999999)
   USAGE(XMITQ)                            TRIGGER
   TRIGTYPE(FIRST)                         TRIGDPTH(1)
   TRIGMPRI(0)                             QDEPTHHI(80)
   QDEPTHLO(20)                            QDPMAXEV(ENABLED)
   QDPHIEV(ENABLED)                        QDPLOEV(DISABLED)
   QSVCINT(999999999)                      QSVCIEV(NONE)
   DISTL(YES)                              NPMCLASS(NORMAL)
   DEFTYPE(PREDEFINED)                     TYPE(QLOCAL)
   SCOPE(QMGR)                             DEFBIND(OPEN)
   IPPROCS(1)                              OPPROCS(2)
   CURDEPTH(0)                         
3 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.

Now the one that seems to misbehave

Used
display channel(CRANE2.TO.HCPDCMS) all
display channel(HCPDCMS.TO.CRANE2) all
dis ql(HCPDCMS.XMIT.QUEUE)
Code:

Result
5724-B41 (C) Copyright IBM Corp. 1994, 2002.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager HCPDCMS.

     1 : display channel(CRANE2.TO.HCPDCMS) all
AMQ8414: Display Channel details.
   CHANNEL(CRANE2.TO.HCPDCMS)              CHLTYPE(RQSTR)
   TRPTYPE(TCP)                            DESCR(Inbound channel from CRANE2)
   MCANAME( )                              MODENAME( )
   TPNAME( )                               BATCHSZ(50)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        PUTAUT(DEF)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlwol-hcpdcrn2(1414))          MREXIT( )
   MRDATA( )                               MRRTY(10)
   MRTMR(1000)                             HBINT(5)
   NPMSPEED(FAST)                          SSLCIPH( )
   SSLCAUTH(REQUIRED)                      LOCLADDR( )
   KAINT(AUTO)                             MCAUSER( )
   ALTDATE(2016-06-13)                     ALTTIME(15.02.11)
   SSLPEER()                           
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
     2 : display channel(HCPDCMS.TO.CRANE2) all
AMQ8414: Display Channel details.
   CHANNEL(HCPDCMS.TO.CRANE2)              CHLTYPE(SVR)
   TRPTYPE(TCP)                            DESCR(Outbound channel to CRANE2)
   XMITQ(CRANE2.XMIT.QUEUE)                MCANAME( )
   MODENAME( )                             TPNAME( )
   BATCHSZ(50)                             DISCINT(0)
   SHORTRTY(7200)                          SHORTTMR(5)
   LONGRTY(999999999)                      LONGTMR(20)
   SCYEXIT( )                              SEQWRAP(999999999)
   MAXMSGL(4194304)                        CONVERT(NO)
   SCYDATA( )                              USERID( )
   PASSWORD( )                             MCATYPE(PROCESS)
   CONNAME(stlwol-hcpdcrn2(1414))          HBINT(5)
   BATCHINT(0)                             NPMSPEED(FAST)
   SSLCIPH( )                              SSLCAUTH(REQUIRED)
   BATCHHB(0)                              LOCLADDR( )
   KAINT(AUTO)                             MCAUSER( )
   ALTDATE(2016-06-13)                     ALTTIME(15.02.29)
   SSLPEER()                           
   MSGEXIT( )                           
   SENDEXIT( )                         
   RCVEXIT( )                           
   MSGDATA( )                           
   SENDDATA( )                         
   RCVDATA( )                           
     3 : display ql(CRANE2.XMIT.QUEUE)
AMQ8409: Display Queue details.
   DESCR(Transmit Queue to CRANE2)         PROCESS( )
   BOQNAME( )                              INITQ(SYSTEM.CHANNEL.INITQ)
   TRIGDATA(HCPDCMS.TO.CRANE2)             CLUSTER( )
   CLUSNL( )                               QUEUE(CRANE2.XMIT.QUEUE)
   CRDATE(2009-03-31)                      CRTIME(12.37.39)
   ALTDATE(2016-07-15)                     ALTTIME(10.29.21)
   GET(ENABLED)                            PUT(ENABLED)
   DEFPRTY(5)                              DEFPSIST(YES)
   MAXDEPTH(5000)                          MAXMSGL(4194304)
   BOTHRESH(0)                             SHARE
   DEFSOPT(EXCL)                           HARDENBO
   MSGDLVSQ(FIFO)                          RETINTVL(999999999)
   USAGE(XMITQ)                            TRIGGER
   TRIGTYPE(FIRST)                         TRIGDPTH(1)
   TRIGMPRI(0)                             QDEPTHHI(80)
   QDEPTHLO(20)                            QDPMAXEV(ENABLED)
   QDPHIEV(ENABLED)                        QDPLOEV(DISABLED)
   QSVCINT(999999999)                      QSVCIEV(NONE)
   DISTL(YES)                              NPMCLASS(NORMAL)
   DEFTYPE(PREDEFINED)                     TYPE(QLOCAL)
   SCOPE(QMGR)                             DEFBIND(OPEN)
   IPPROCS(1)                              OPPROCS(2)
   CURDEPTH(0)                         

3 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jul 18, 2016 2:54 pm    Post subject: Reply with quote

Poobah

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

Andrew.Potter wrote:
Then we have four (4) cranes running their own queue managers ...

Cranes??

Crane | Definition of Crane by Merriam-Webster
www.merriam-webster.com/dictionary/crane
Merriam‑Webster
Simple Definition of crane. : a big machine with a long arm that is used by builders for lifting and moving heavy things. : a type of tall bird that has a long neck and long legs and lives near water.
_________________
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: Tue Jul 19, 2016 5:03 am    Post subject: Reply with quote

Grand High Poobah

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

ADOPT NEW MCA should help some. The rest is probably due to poor wireless signal.

You specified your version at 5.3. This version is over 10 years old and has been out of support for quite some time now. You might want to look into upgrading your infrastructure.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PaulClarke
PostPosted: Tue Jul 19, 2016 10:37 am    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

Are you sure you are waiting long enough? Heartbeat interval has a big effect on how quickly MQ channels will detect a failure. For example, a channel will detect a failure in 10 seconds, for HBINT(5) where as it will take two minutes for HBINT(60) which is an awfully long time if you are sitting there waiting.

Having said that over the years the MQ code got better and better at detecting network failures and version 5.3 is very old. I couldn't say for certain how good it was in various circumstances. I agree with fjb_saper you would be better off to move to a later version of MQ.

Cheers,

Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
Andrew.Potter
PostPosted: Tue Jul 19, 2016 4:14 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

fjb_saper and Paul,

Your comments re the age are noted.

We have just upgraded the computers in the cranes to Windows 7 (from XP) and one of them currently has MQ v7.5. The second of the problem cranes will be upgraded to MQ 7.5 in the next week or so.

It is still showing similar issues.

Unfortunately the Server end is currently running under windows Server 2003 and getting that upgraded is easier said than done.

It is not likely to happen quickly.

I do realize that the Wireless is the root cause.

When we do have an issue we can connect to the crane remotely, via the wireless but the channels require manual intervention to restart.

The required intervention can be as simple as restarting the Requester Channel on the crane (showing as inactive) or, at worst, it requires stopping both channels on the crane, both channels on the server, then resetting the message numbers and then restarting the channels at both ends.

Andrew
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Jul 19, 2016 4:40 pm    Post subject: Reply with quote

Poobah

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

Please provide some more detail about your wireless configuration. Is it EDACS? Bluetooth? Line-of-sight? What frequencies? What distances?

MQ+wireless is not new.
_________________
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
Andrew.Potter
PostPosted: Tue Jul 19, 2016 6:19 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

802.11g WIFI

Building is 300m Long with two (2) Access Points.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Jul 19, 2016 7:50 pm    Post subject: Reply with quote

Poobah

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

Andrew.Potter wrote:
802.11g WIFI

Building is 300m Long with two (2) Access Points.

Only two for a 300 meter blldg? Metal partitions/walls? Lots of electrical?

Make/model of access points? Home type? Or industrial?

Get ahold of a professional signal strength meter; and map out the whole bldg looking for weak/dead spots. Reposition WAPs or install more of 'em.
_________________
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: Tue Jul 19, 2016 7:52 pm    Post subject: Reply with quote

Padawan

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

Looking at your definitions, I'd summarise your channel set up as follows.

You use SVR - RQSTR pairs with connection names filled in on both sides, thus allowing the channels to be manually started from either end. You have DISCINT(0) which suggests you expect and wish these channels to be running all the time. However, you also have triggering to automatically start these channels when work arrives on the transmit queue, should they not already be running.

Andrew.Potter wrote:
The only difference is in the heartbeat. I changed this from 5 to 60 on the crane side to try and avoid the cache and resources being flushed too often, I am sure I read that somewhere on this forum. It was originally the same as crane 5 (set at 5), but we send a loopback message that is targeted for every 5 seconds. I believe changing the heartbeat to 60 seconds should have helped more than hindered, but maybe i am wrong.

I do realise that on channel start up MQ will negotiate and use the 60 second heartbeat from the crane rather than the 5 from the server side, as it is longer.


You are correct in your latter statement, that the change you made to heartbeats is not making any difference because MQ will negotiate them to the longer interval.

Andrew.Potter wrote:
We have a couple of channels that operate over wireless connections. When the wireless connection
is dropped for whatever reason the channels do not always reconnect/restart seamlessly.


In order for the channels to automatically restart, the SVR end (which is the only end with RETRY capabilities) has to notice the connection has been dropped. How long do you wait before you decide it hasn't noticed? It certainly won't notice any earlier than 2 x 60 seconds with your current setup.

Could you show the CHSTATUS at both ends when you realise the connection has been dropped?

Andrew.Potter wrote:
The required intervention can be as simple as restarting the Requester Channel on the crane (showing as inactive)


This I suspect might just be not waiting long enough for the SVR end to detect the failure since your heartbeats are 60 seconds apart. If you have AdoptMCA configured, then restarting the RQSTR into the SVR means that the SVR will be booted out when it hasn't yet noticed the loss of connectivity.

Andrew.Potter wrote:
or, at worst, it requires stopping both channels on the crane, both channels on the server, then resetting the message numbers and then restarting the channels at both ends.


This is worrisome. If you have to reset the message sequence numbers then something is going more awry than just a simple network connection drop. Could you show an example of the difference in the sequence numbers, i.e. the error message, that indicates you need to do the RESET.

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
Andrew.Potter
PostPosted: Tue Jul 19, 2016 8:37 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

Morag,

Thanks for your detailed reply, it is heartening to see that I do have some things correct, even though my knowledge is very limited.

I will gather some meaningful answers and give a more meaningful reply at a later time.

Andrew
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Jul 20, 2016 3:46 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

I realize this is more work.

But using MQTT may be a much better solution to talk to/from the cranes and the queue manager.

MQTT is designed specifically for this kind of unreliable network and devices/things/cranes that are disconnected from the network at some regular frequency.

You can use the MQ Telemetry bridge that comes with MQ to connect MQTT clients on the cranes to your queue managers. You could also use MessageSight for this, with better performance and some more flexibility - including better security and the ability to route messages to different queue managers based on the topics they are published to. MQTT is pub/sub only.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Jul 20, 2016 4:18 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqjeff wrote:
But using MQTT may be a much better solution to talk to/from the cranes and the queue manager.




mqjeff wrote:
MQTT is designed specifically for this kind of unreliable network and devices/things/cranes that are disconnected from the network at some regular frequency.




mqjeff wrote:
I realize this is more work.


But given that you've got to move off v5.3 anyway (and you have to; you just have to) and you've got a specific and demonstrable problem that you can put in front of management to gain time & budget for the work then this is a very good solution for your problem.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Andrew.Potter
PostPosted: Wed Jul 20, 2016 1:50 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

Thanks for the input Guys.

I will investigate MQTT, I currently have no knowledge of this at all.

Thanks
Back to top
View user's profile Send private message
Andrew.Potter
PostPosted: Wed Jul 20, 2016 2:18 pm    Post subject: Reply with quote

Newbie

Joined: 18 Jul 2016
Posts: 7

Last night we had another stoppage on Crane 1. This is a unit that currently has MQ 7.5.0.5 (32 bit windows) installed, the Server side is still v5.3.

The fix was to manually start the Requester channel on the Crane. It was reported a being in "inactive" state. Once the channel was started then the requester channel changed to running, and more importantly message flow then resumed.

Am I correct in deducing that this means the server end did not recognise that the connection had been dropped, since it appears no attempts were made to restart it from that end.

Logs from crane end at the relevant times are shown below. Unfortunately I do not have logs from the server end as they have rotated. I have changed the log settings on our development system to ensure a logger time frame is logged. If this is OK I will propagate to the production server.


The way I read these logs is that the crane did see connection fail on its server channel at 2:18am (TCP failure) and successfully restarts that channel "crane1.to.hcpdcms".
The at 2:19:39 the crane requester queue times out (120 seconds).

It is then restarted manually at 3:22am


-------------------------------------------------------------------------------
7/21/2016 02:18:25 - Process(1020.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9208: Error on receive from host stlhcpdwol-csprodap1 (10.18.78.41)(1415).

EXPLANATION:
An error occurred receiving data from stlhcpdwol-csprodap1 (10.18.78.41)(1415)
over TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10053 (X'2745'). Record these
values and tell the systems administrator.
----- amqccita.c : 4065 -------------------------------------------------------
7/21/2016 02:18:25 - Process(1020.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9999: Channel 'CRANE1.TO.HCPDCMS' to host
'stlhcpdwol-csprodap1.stlwol.bsl.net(1415)' ended abnormally.

EXPLANATION:
The channel program running under process ID 1020(3076) for channel
'CRANE1.TO.HCPDCMS' ended abnormally. The host name is
'stlhcpdwol-csprodap1.stlwol.bsl.net(1415)'; 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 : 1064 -------------------------------------------------------
7/21/2016 02:18:27 - Process(6588.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9002: Channel 'CRANE1.TO.HCPDCMS' is starting.

EXPLANATION:
Channel 'CRANE1.TO.HCPDCMS' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
7/21/2016 02:19:39 - Process(5368.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9259: Connection timed out from host '10.18.78.41(1415)'.

EXPLANATION:
A connection from host '10.18.78.41(1415)' over TCP/IP timed out.
ACTION:
The select() [TIMEOUT] 120 seconds call timed out. Check to see why data was
not received in the expected time. Correct the problem. Reconnect the channel,
or wait for a retrying channel to reconnect itself.
----- amqccita.c : 4445 -------------------------------------------------------
7/21/2016 02:19:39 - Process(5368.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9999: Channel 'HCPDCMS.TO.CRANE1' to host
'stlhcpdwol-csprodap1.stlwol.bsl.net(1415)' ended abnormally.

EXPLANATION:
The channel program running under process ID 5368(3948) for channel
'HCPDCMS.TO.CRANE1' ended abnormally. The host name is
'stlhcpdwol-csprodap1.stlwol.bsl.net(1415)'; 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 : 1064 -------------------------------------------------------
7/21/2016 03:22:01 - Process(6668.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
Host(STLWOL-HCPDCRN1) Installation(HCPDCranes)
VRMF(7.5.0.5) QMgr(CRANE1)

AMQ9002: Channel 'HCPDCMS.TO.CRANE1' is starting.

EXPLANATION:
Channel 'HCPDCMS.TO.CRANE1' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Windows Configuration
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.