| Author |
Message
|
| rammer |
 Posted: Wed Nov 05, 2014 12:13 pm Post subject: Ending channels |
 |
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
MQ 7.5
AIX
I have a query over stauts of channels
Looking at channel status now I have 1 channel that started 7 hours ago and the last message received over the channel was 5 hours ago.
The channel is a SVRCONN and looking at the RAPPLTAG a tester had RFHUTIL connected to it.
The settings on the channel are
DISCINT(0)
KAINT(AUTO)
HBINT(300)
Reading the MQ 7.5 Info Centre it mentions DISCINT default is 300, which I thoguht it would mean that the channel would end at that period. However all the SVRCONNS I look at are set as 0 for default. Im presuming there may be something else that can be set / tweaked to end channels that are not in use?
in qm.ini I have
Channels:
MQIBindType=FASTPATH
AdoptNewMCA=ALL
AdoptNewMCATimeout=60
AdoptNewMCACheck=ALL
MaxChannels=50
MaxActiveChannels=50
Thank you |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 05, 2014 12:23 pm Post subject: Re: Ending channels |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rammer wrote: |
| Reading the MQ 7.5 Info Centre it mentions DISCINT default is 300, which I thoguht it would mean that the channel would end at that period. |
Yes.
| rammer wrote: |
| However all the SVRCONNS I look at are set as 0 for default. |
No, they're set to 0. The default (as supplied by IBM) remains 300. Either these channels have been deliberately set to 0, or the default at your site has been changed to 0. I would suspect the former.
| rammer wrote: |
| Im presuming there may be something else that can be set / tweaked to end channels that are not in use? |
No, IBM have provided DISCINT as a mechanism. If you want channels to disconnect when not in use, you set this to the value you want. Or you set it to 0 to disable the mechanism.
The question is not what else can you set, by why can't you set this? Which links to the question of why someone at your site changed it from the default.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Nov 05, 2014 12:37 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| The KC I read for SVRCONN has 0 as default for DISCINT... and I'm look'n at MQ 7.5 |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Nov 05, 2014 12:41 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Hi Vitor
I can say that nobody has changed it to 0 from what I can see.
I have a copy of MQ 7.5 on my laptop and just checked the SYSTEM.DEF.SVRCONN channel and that is also set to 0.
And I have just gone back to the unix machine and created a queue manager in your honour and that is set to 0 as well..
QMNAME(VITOR)
DIS CHANNEL(VITOR.SVRCONN) DISCINT
4 : DIS CHANNEL(VITOR.SVRCONN) DISCINT
AMQ8414: Display Channel details.
CHANNEL(VITOR.SVRCONN) CHLTYPE(SVRCONN)
DISCINT(0)
Mq Version is 7.5.0.1
THanks |
|
| Back to top |
|
|
| rammer |
| Posted: Wed Nov 05, 2014 12:44 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
This is what I see in the 7.5 Info Centre
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.con.doc/q081860_.htm
The default DISCINT value is set to 100 minutes. However, a value of a few minutes is often a reasonable value to use without impacting performance or keeping channels running for unnecessarily long periods of time. If it is appropriate for your environment you can change this value, either on each individual channel or through changing the value in the default channel definitions, for example SYSTEM.DEF.SENDER. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Nov 05, 2014 12:48 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
|
| Back to top |
|
|
| rammer |
| Posted: Wed Nov 05, 2014 12:52 pm Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Good Spot Joseph, looks to me the documentation contradicts itself.
By the way I live in Derby in England. hope the Derby you live in is warmer than mine at the moment!. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Nov 05, 2014 1:02 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Derby City USA is where the Kentucky Derby is run (of course the most famous of all horse races). It is cold and raining and likely to be a very cold winter.
For the true defaults for the different channels, always go to the Reference section and MQSC part. Different channel types have different defaults and some times it is even different between platforms like distributed vs z/OS. The link you had was talking about SENDER channels as an example. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 05, 2014 1:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rammer wrote: |
I can say that nobody has changed it to 0 from what I can see.
I have a copy of MQ 7.5 on my laptop and just checked the SYSTEM.DEF.SVRCONN channel and that is also set to 0.
And I have just gone back to the unix machine and created a queue manager in your honour and that is set to 0 as well.. |
So whatever caused the value to be set to 0 on your site (new default value in 7.5, site override, etc) is still working. Who would have guessed....? 
The question remains why are you looking for a different mechanism to DISCINT?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Wed Nov 05, 2014 1:19 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
The different defaults for the different channel types are entirely intentional and not a typo. A disconnect for a SENDER channel is a mere efficiency thing. Setting it to a high or low value just changes the resource usage. It will not ultimately affect the operation of the channel or how many messages get through the channel. It only decides how regularly the channel should end when it has nothing to do.
However, on a SVRCONN the DISCINT value is a lot more intrusive. If you set a non-zero vaoue then 'potentially' you are going kill a perfectly valid and working client connection. Just because an MQ application connected 7 hours ago and hasn't issued a single API does not suggest that anything is wrong. If you decide to kill them after 7 hours of inactivity then by all means set the DISCINT value but be prepared for the phone calls asking why they are getting MQRC_CONNECTION_BROKEN reason codes (or whatever error actually results which frankly I can't remember). Anyway, it is to avoid the risk of upset application users that the defualt of DISCINT is 0 on SVRCONNs
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 05, 2014 1:23 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
|
|
