| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| HBINT doesnt help to keep channel RUNNING |
« View previous topic :: View next topic » |
| Author |
Message
|
| jaswant.bea979 |
 Posted: Thu Mar 29, 2018 10:41 am Post subject: HBINT doesnt help to keep channel RUNNING |
 |
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
Hi,
I'm trying to understand HBINT parameter. As per documentation it is :
| Quote: |
| Heartbeat flows unblock the receiving MCA, which is waiting for messages to arrive or for the disconnect interval to expire. When the receiving MCA is unblocked, it can disconnect the channel without waiting for the disconnect interval to expire. |
Does heartbeat suppose to help keep Channel RUNNING or it helps with disconnect?
I tested HBINT and it does send packets (BYTSSENT increases and MSGS is zero...thanks Morag) across the channel but still channel ends after DISCINT .
| Code: |
HBINT is set to 10 on SDR and RCVR. Verified using chs.
DISCINT set to 60 and channel got disconnected after 60 secs even though
BYTSSENT increased after HBINT value.
dis chs (QM75WIN.TO.QM80LNX) all
4 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(6) BUFSSENT(6)
BYTSRCVD(408) BYTSSENT(408)
CHSTADA(2018-03-29) CHSTATI(14.26.10)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(38AAA65AB56BA114)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(00004AD500000001) LOCLADDR(180.211.22.67(57176))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(MQGET) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
:
dis chl (QM75WIN.TO.QM80LNX) all
5 : dis chl (QM75WIN.TO.QM80LNX) all
AMQ8414: Display Channel details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
ALTDATE(2018-03-29) ALTTIME(14.25.55)
BATCHHB(0) BATCHINT(0)
BATCHLIM(5000) BATCHSZ(50)
CERTLABL( ) COMPHDR(NONE)
COMPMSG(NONE) CONNAME(180.211.22.67(1419))
CONVERT(NO) DESCR( )
DISCINT(60) HBINT(10)
KAINT(AUTO) LOCLADDR( )
LONGRTY(999999999) LONGTMR(1200)
MAXMSGL(4194304) MCANAME( )
MCATYPE(PROCESS) 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(CN=QM80LNX,O=IBM,C=USA) STATCHL(QMGR)
TPNAME( ) TRPTYPE(TCP)
USEDLQ(YES) USERID( )
XMITQ(QM80LNX) |
| Code: |
dis chl (QM75WIN.TO.QM80LNX) all
1 : dis chl (QM75WIN.TO.QM80LNX) all
AMQ8414: Display Channel details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE([b]RCVR[/b])
ALTDATE(2018-03-14) ALTTIME(10.21.17)
BATCHSZ(50) CERTLABL( )
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) HBINT(300)
KAINT(AUTO) MAXMSGL(4194304)
MCAUSER( ) MONCHL(QMGR)
MRDATA( ) MREXIT( )
MRRTY(10) MRTMR(1000)
MSGDATA( ) MSGEXIT( )
NPMSPEED(FAST) PUTAUT(DEF)
RCVDATA( ) RCVEXIT( )
RESETSEQ(NO) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SEQWRAP(999999999)
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER(CN=QM75WIN,O=IBM,C=USA) STATCHL(QMGR)
TRPTYPE(TCP) USEDLQ(YES)
|
| Code: |
dis chs (QM75WIN.TO.QM80LNX) all
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(RCVR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(2) BUFSSENT(2)
BYTSRCVD(296) BYTSSENT(296)
CHSTADA(2018-03-29) CHSTATI(14.25.28)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67) CURLUWID(0000000000000000)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000069CB000008DF) LOCLADDR(180.211.22.67(1419))
LSTLUWID(0000000000000000) LSTMSGDA( )
LSTMSGTI( ) LSTSEQNO(0)
MCASTAT(RUNNING) MCAUSER(mqm)
MONCHL(OFF) MSGS(0)
NPMSPEED(FAST) RQMNAME(QM75WIN)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(RECEIVE) XBATCHSZ(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
|
QM Log file :
| Code: |
3/29/2018 02:26:10 PM - Process(19157.1) User(mqm) Program(runmqchl)
Host(xxxxx) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9002: Channel 'QM75WIN.TO.QM80LNX' is starting.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
03/29/2018 02:27:10 PM - Process(19157.1) User(mqm) Program(ru nmqchl)
Host(xxxxx) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' closed because no messages arrive d on the
transmission queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------- -----------------
03/29/2018 02:27:10 PM - Process(19157.1) User(mqm) Program(ru nmqchl)
Host(xxxxx) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9001: Channel 'QM75WIN.TO.QM80LNX' ended normally.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' to host '180.211.22.67(1419)' end ed normally.
ACTION:
None.
-------------------------------------------------------------- -----------------
|
Thanks[/quote] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 29, 2018 11:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Is it fair to say this is part 2 of this epic? Which started out because the SVRCONN channel shows INACTIVE rather than RUNNING? And all the help in that thread has failed to dissuade you that, somehow, it should show as RUNNING?
You also mentioned (way back) on that thread that you started this because once the channel "stopped" the application had to be restarted to reestablish the connection, and you decided the best way to prevent this was to keep the channel up no matter what was using it. Did you look into the code to see why it can't re-establish the connection? Like what MQ reason code it gets when it tries? Or did you blindly latch onto restarting the application and go from there?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2018 11:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Am I also correct in saying that the OS involved is Windows?
I infer this both from the name of the queue manager and the instinctive restart of a failing component.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jaswant.bea979 |
| Posted: Thu Mar 29, 2018 11:37 am Post subject: |
|
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
No sir  . In this question I'm trying to understand HBINT behaviour in SDR > RCVR channel. No SVRCONN is involved here.
Also, In this case both QMs, SDR and RCVR , on the same Linux (RHEL) machine. No Load balancer involved here. I was following a IBM documentation which uses QM75WIN on windows to show SDR > RCVR communication . I dont have access on my windows laptop so I created the same QM75WIN on linux. My apologies for making this confusing. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2018 11:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jaswant.bea979 wrote: |
| No sir . In this question I'm trying to understand HBINT behaviour in SDR > RCVR channel. No SVRCONN is involved here. |
This is available in your original post (rereading it) but you could have emphasized the point....... 
I'm unclear what you're unclear on. The HBINT is part of the disconnect process as laid out in the documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jaswant.bea979 |
| Posted: Thu Mar 29, 2018 12:15 pm Post subject: |
|
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
In other products HEARTBEAT usually means sending a packet to keep connection up to avoid disconnect and that confuses me with IBM MQ definition of HBINT. So i erased what usually heartbeat means and tried to see the behavior of SDR > RCVR channel and found DISCINT does disconnect after idle time interval.
So I'm not getting what HBINT does? Per documentation I kept is lower than DSCINT.
HBINT is 10
DISCINT is 60. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 29, 2018 7:53 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jaswant.bea979 wrote: |
In other products HEARTBEAT usually means sending a packet to keep connection up to avoid disconnect and that confuses me with IBM MQ definition of HBINT. So i erased what usually heartbeat means and tried to see the behavior of SDR > RCVR channel and found DISCINT does disconnect after idle time interval.
So I'm not getting what HBINT does? Per documentation I kept is lower than DSCINT.
HBINT is 10
DISCINT is 60. |
IIRC HBINT is tricky in such a way that it does not take the lower of the negotiated values but the higher one.
So if on one side of the channel your HBINT is 10 and on the other side it is 300, your actual HBINT is 300...
Best check using the channel status.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Mar 30, 2018 5:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Let's back up and discuss "RUNNING" state.
RUNNING simply means that either 1) the channel is currently transmitting messages; OR, 2) if the channels is NOT transmitting message, it believes that it will be able to transmit messages the next time it tries to do so.
After two heartbeats, with no messages to transmit, disconnect interval tells the channel to go into INACTIVE state. This allows both ends of the channels to close queues - to free up RAM and the channel processes. The purpose of disconnect is/was to conserve resources. Conservation of resources was far more important in the old days of single processor hardware, limited RAM, and less reliable networks.
If there are no messages to be transmitted, AND if heartbeats are infrequent like 5 minutes apart, AND someone cuts the CAT5 cable with a knife 1 second after the most recent heartbeat, then the channel will blissfully stay in RUNNING for 4 minutes 59 seconds (approximately) before it will discover that the channel is incapable of transmitting messages.
If there are no messages to be transmitted, AND if heartbeats are more frequent, then the channel will discover the cut cable sooner, and drive the retry activity sooner to restart the channel. The RETRY values tell channel software how often over given time-frame to attempt to restart the channel. Channel retry software cannot repair cut cables.
If your channel is continuously transmitting messages, then it will likely never go into INACTIVE state.
_________________
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 |
|
|
| mvic |
| Posted: Fri Mar 30, 2018 7:01 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jaswant.bea979 wrote: |
| So I'm not getting what HBINT does? Per documentation I kept is lower than DSCINT. |
MQ heartbeat is a bit similar in concept to TCP keepalive.
One side sends a little packet saying "I'm still alive, are you?", and expects to receive one in reply.
It means the channel can be closed on the local side if the remote side is not there any more, and this can be detected "soon" after it happens, if this is what you need.
For obvious reasons it is not wise to set a small number for HBINT. |
|
| Back to top |
|
|
| jaswant.bea979 |
| Posted: Fri Mar 30, 2018 7:11 am Post subject: |
|
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
bruce2359 wrote:
Let's back up and discuss "RUNNING" state.
After two heartbeats, with no messages to transmit, disconnect interval tells the channel to go into INACTIVE state.
Thank you the reply. But looks like this INACTIVE piece is not working.
I tested with :
HBINT = 10
DISCINT =60
Both QMs are on same linux server.
From error logs ( I have pasted error log at the bottom)
start time - 03/30/2018 10:32:07 AM
end time - 03/30/2018 10:33:09 AM
Reason for end - AMQ9545: Disconnect interval expired.
I have a script which prints the date/time and channel status after 13 secs . 13 secs is to keep track what happens after 10 secs of HBINT.
Observation -
BYTSSENT kept increasing with 28 bytes after 10 secs.
MSGS stayed zero because I didnt send any message.
Channel disconnected after 62 secs and reason was AMQ9545.
After two HBINT, around 10:32:27, CHL should have gone to INACTIVE. It didnt happen.
STATUS changed to STOPPING around 10:33:08 and this may explain why we are seeing 62 secs for disconnection instead 60 secs (DISCINT 60)
So, looks like HBINT does sends beats but it does NOT change channel behaviour. Im back to square one. what is the use of HBINT ?
| Code: |
SCRIPT OUTPUT:
-ksh-4.2$ ./1.sh
-----------------------------------------------------
time is Fri Mar 30 10:32:02 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8420: Channel Status not found.
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:32:15 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(1) BUFSSENT(1)
BYTSRCVD(268) BYTSSENT(268)
CHSTADA(2018-03-30) CHSTATI(10.32.07)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(AC49BE5A45A33B13)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000063D000000001) LOCLADDR(180.211.22.67(43080))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(MQGET) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:32:28 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(3) BUFSSENT(3)
BYTSRCVD(324) BYTSSENT(324)
CHSTADA(2018-03-30) CHSTATI(10.32.07)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(AC49BE5A45A33B13)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000063D000000001) LOCLADDR(180.211.22.67(43080))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(MQGET) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:32:41 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(4) BUFSSENT(4)
BYTSRCVD(352) BYTSSENT(352)
CHSTADA(2018-03-30) CHSTATI(10.32.07)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(AC49BE5A45A33B13)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000063D000000001) LOCLADDR(180.211.22.67(43080))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(MQGET) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:32:55 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(5) BUFSSENT(5)
BYTSRCVD(380) BYTSSENT(380)
CHSTADA(2018-03-30) CHSTATI(10.32.07)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(AC49BE5A45A33B13)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000063D000000001) LOCLADDR(180.211.22.67(43080))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(RUNNING) STOPREQ(NO)
SUBSTATE(MQGET) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:33:08 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8417: Display Channel Status details.
CHANNEL(QM75WIN.TO.QM80LNX) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(6) BUFSSENT(7)
BYTSRCVD(408) BYTSSENT(444)
CHSTADA(2018-03-30) CHSTATI(10.32.07)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(180.211.22.67(1419)) CURLUWID(AC49BE5A45A33B13)
CURMSGS(0) CURRENT
CURSEQNO(0) EXITTIME(0,0)
HBINT(10) INDOUBT(NO)
JOBNAME(000063D000000001) LOCLADDR(180.211.22.67(43080))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA( ) LSTMSGTI( )
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QM80LNX) SHORTRTS(10)
SECPROT(NONE) SSLCERTI( )
SSLKEYDA( ) SSLKEYTI( )
SSLPEER( ) SSLRKEYS(0)
STATUS(STOPPING) STOPREQ(NO)
SUBSTATE( ) XBATCHSZ(0,0)
XMITQ(QM80LNX) XQTIME(0,0)
RVERSION(08000005) RPRODUCT(MQMM)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
Sleeping for 13 secs...
-----------------------------------------------------
time is Fri Mar 30 10:33:21 EDT 2018
Going to display channel status....
5724-H72 (C) Copyright IBM Corp. 1994, 2015.
Starting MQSC for queue manager QM75WIN.
1 : dis chs (QM75WIN.TO.QM80LNX) all
AMQ8420: Channel Status not found.
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
Sleeping for 13 secs.. |
.
Error Log:
| Code: |
03/30/2018 10:32:07 AM - Process(25552.1) User(mqm) Program(runmqchl)
Host(xxxxp) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9002: Channel 'QM75WIN.TO.QM80LNX' is starting.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
tail: AMQERR01.LOG: file truncated
03/30/2018 10:33:09 AM - Process(25130.4) User(mqm) Program(amqzmur0)
Host(xxxxp) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ6287: WebSphere MQ V8.0.0.5 (p800-005-160516.2).
EXPLANATION:
WebSphere MQ system information:
Host Info :- Linux 3.10.0-693.1.1.el7.x86_64 (MQ Linux (x86-64
platform) 64-bit)
Installation :- /opt/mqm (Installation1)
Version :- 8.0.0.5 (p800-005-160516.2)
ACTION:
None.
-------------------------------------------------------------------------------
03/30/2018 10:33:09 AM - Process(25552.1) User(mqm) Program(runmqchl)
Host(xxxxp) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' closed because no messages arrived on the
transmission queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
03/30/2018 10:33:09 AM - Process(25552.1) User(mqm) Program(runmqchl)
Host(xxxxp) Installation(Installation1)
VRMF(8.0.0.5) QMgr(QM75WIN)
AMQ9001: Channel 'QM75WIN.TO.QM80LNX' ended normally.
EXPLANATION:
Channel 'QM75WIN.TO.QM80LNX' to host '180.211.22.67(1419)' ended normally.
ACTION: |
|
|
| Back to top |
|
|
| mvic |
| Posted: Fri Mar 30, 2018 7:17 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jaswant.bea979 wrote: |
| So, looks like HBINT does sends beats but it does NOT change channel behaviour. Im back to square one. what is the use of HBINT ? |
See my post. |
|
| Back to top |
|
|
| jaswant.bea979 |
| Posted: Fri Mar 30, 2018 7:48 am Post subject: |
|
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
| mvic wrote: |
| jaswant.bea979 wrote: |
| So, looks like HBINT does sends beats but it does NOT change channel behaviour. Im back to square one. what is the use of HBINT ? |
See my post. |
Thanks. I am a bit clear now
May i dare to ask, in my case, HBINT sends packets every 10 secs and since it is getting reply back connection stays up till DISCINT kicks in. Does HBINT packet not count ? I mean packets are flowing every 10 secs and still DISCINT kicks in and ends the channel. Channel should stay up since it is NOT ideal. right? |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Mar 30, 2018 7:59 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| jaswant.bea979 wrote: |
| HBINT sends packets every 10 secs and since it is getting reply back connection stays up till DISCINT kicks in. Does HBINT packet not count ? I mean packets are flowing every 10 secs and still DISCINT kicks in and ends the channel. Channel should stay up since it is NOT ideal. right? |
HBINT defines how often the heartbeat is sent.
DISCINT defines how long the channel remains up, even though it has no work to do.
Heartbeating helps detect network or other problems in a timely way. It sounds like you didn't have any, so heartbeating detected no issue.
But it sounds like you wanted the channel to go inactive after a period when no msgs were sent, because you had set a nonzero DISCINT.
If you do not want the channel to go inactive after a period when no msgs are sent, then set DISCINT(0).
Some people want their channels to be RUNNING all the time, so there is minimal latency when a message is placed on the xmitq on the SDR side.
Other people are willing to take a small cost of starting an INACTIVE channel, so that they can save the resources (mainly memory, threads, and the regular but small cost of heartbeating) it takes to have one sitting in RUNNING state with nothing to do.
The thing is, that "small" cost might conceivably be several seconds in some environments, and this can cause missed SLAs in some applications.
I don't know about your case, though. |
|
| Back to top |
|
|
| jaswant.bea979 |
| Posted: Fri Mar 30, 2018 8:29 am Post subject: |
|
|
Novice
Joined: 15 Mar 2018
Posts: 16
|
| Thank you for explanation. It clear now. In my case we dont want to keep no latency. Front end handles ( apache web-server) almost 14k-15k transactions per second and then we have java container ( weblogic) doing many things and one of them is connect to MQ ( a few are synchronous calls) . Weblogic uses MQ client and BINDING files to make the calls to MQ. Any latency anywhere means web-servers start choking up. We have web-servers limit setup to 18k. Any request beyond that is 500 error. MQ has been pretty stable . |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Apr 02, 2018 4:03 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| jaswant.bea979 wrote: |
| Thank you for explanation. It clear now. In my case we dont want to keep no latency. Front end handles ( apache web-server) almost 14k-15k transactions per second and then we have java container ( weblogic) doing many things and one of them is connect to MQ ( a few are synchronous calls) . Weblogic uses MQ client and BINDING files to make the calls to MQ. Any latency anywhere means web-servers start choking up. We have web-servers limit setup to 18k. Any request beyond that is 500 error. MQ has been pretty stable . |
Ensure your MQ Client interface is using some sort of connection pooling or is holding connections for use by multiple transactions. If the interface is putting to or getting from the same queue over multiple transactions, try to keep the queue open across multiple transactions.
Connection and Open Queue are the two most expensive operations in MQ. For best performance, avoid doing these as much as possible.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
