|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Parameter "msgs" Server Connection Channel Status |
« View previous topic :: View next topic » |
Author |
Message
|
krypton |
Posted: Sun May 06, 2018 10:01 am Post subject: Parameter "msgs" Server Connection Channel Status |
|
|
 Disciple
Joined: 14 Mar 2010 Posts: 186
|
Hi,
according to IBM documentations, the parameter "msgs" in the channel status for server connection channel it defines the number of MQI calls handled.
I just checked the value of this parameter in our production system and found it is a very large number - 2211986 , and this instance of channel was started today only.
I am wondering if such high number of MQI calls is normal from a single client application?
Does this MQI calls corresponding to number of messages being sent by application.
No of MQI calls = No of messages posted by application (??) _________________ Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep. |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun May 06, 2018 11:07 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
With IBM MQ Client bindings, each MQI call is transported cross-network to the SVRCONN channel - not just the MQPUT call to put a message. _________________ 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 |
|
 |
gbaddeley |
Posted: Sun May 06, 2018 4:03 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Is the app doing MQOPEN and MQCLOSE for each msg? MQ also does internal heartbeat messages, and most Client MQI calls will result in 2 messages. _________________ Glenn |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sun May 06, 2018 4:59 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
The app is probably issuing repeated MQGET calls with a small wait interval, or no wait interval at all. Over and over, it issues an MQGET for a message, finds none, and issues the MQGET call again.
This behavior can drive the "msgs" parameter on a SVRCONN channel instance very high, even though there are little to no application messages being passed.
Frequent MQINQ calls will also do it. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
krypton |
Posted: Mon May 07, 2018 3:03 am Post subject: |
|
|
 Disciple
Joined: 14 Mar 2010 Posts: 186
|
Quote: |
The app is probably issuing repeated MQGET calls with a small wait interval, or no wait interval at all. Over and over, it issues an MQGET for a message, finds none, and issues the MQGET call again.
|
It is a batch application which puts large number of messages into Queue. I suspect they are doing repeated number of MQPUT and hence the count of MQI calls has been increasing. _________________ Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|