| Author |
Message
|
| vicks_mq |
 Posted: Tue May 07, 2019 5:02 am Post subject: SVRCONN Last Message Time is getting updated |
 |
|
Disciple
Joined: 03 Oct 2017
Posts: 162
|
We have an application which is connected to MQ Queue manager using SVRCONN channel and I noticed that there has been no transactions happened in the last 24 hours but the LAST MSG TIME on the SVRCONN channel instances keep updated every 1 second.
What could be the reason of this?
MQ version we are using is 8.0.0.10 on LINUX. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue May 07, 2019 10:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 07, 2019 3:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Heartbeats won't drive the LAST MSG TIME, but MQ API calls will.
The term "MSG" is misleading, everyone not surprisingly assumes it means application messages. Why IBM chose to use that term to also cover MQ API calls is one of the mysteries of MQ.
| Quote: |
"but the LAST MSG TIME on the SVRCONN channel instances keep updated every 1 second.
What could be the reason of this? " |
The app is not well written and keeps issuing MQ API calls over that channel every second.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue May 07, 2019 4:44 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Thanks. I stand corrected. (I should not post while taking codeine cough syrup.)
An MQGET with a one second WAITINTERVAL would qualify as not well-written.
_________________
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 |
|
|
| vicks_mq |
| Posted: Wed May 08, 2019 1:54 am Post subject: |
|
|
Disciple
Joined: 03 Oct 2017
Posts: 162
|
| PeterPotkay wrote: |
Heartbeats won't drive the LAST MSG TIME, but MQ API calls will.
The app is not well written and keeps issuing MQ API calls over that channel every second. |
Hi, it seems you are right that is probably the reason, I myself couldnt think of any other reason. |
|
| Back to top |
|
|
| vicks_mq |
| Posted: Wed May 08, 2019 8:03 am Post subject: |
|
|
Disciple
Joined: 03 Oct 2017
Posts: 162
|
| bruce2359 wrote: |
Thanks. I stand corrected. (I should not post while taking codeine cough syrup.)
An MQGET with a one second WAITINTERVAL would qualify as not well-written. |
Hi Bruce, channel substate is showing as "RECEIVING', so I dont think it is MQGET call, in that case the substate will change to "MQWAIT". |
|
| Back to top |
|
|
|
|
