| Author |
Message
|
| tkaravind |
 Posted: Wed Dec 03, 2003 5:39 am Post subject: MAXCHANNELS/MAXACTIVECHANNELS ??? |
 |
|
Acolyte
Joined: 24 Jul 2001
Posts: 64
|
Dear MQ Friends,
Have any of you used MAXCHANNELS/MAXACTIVECHANNELS parameters in your MQSeries environment ?
What for are they used and do they really have any impact on the way QMGR behaves ?
And is there any way we can look at these properties once they are set in an IBM AIX platform ? Any commands available ?
Many Thanks in advance,
Aravind |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Wed Dec 03, 2003 7:02 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
I believe lots of people use them.
You know you need them if you get error such as "AMQ9513: Maximum number of channels reached." You would typically reach this limit for queue managers that have lots of client connections (& therefore channels).
It can be set in the qm.ini file for each qmgr. See the documentation for this but we have:
CHANNELS:
MaxChannels = 1000 ; Maximum number of Channels allowed.
; Default is 100.
MaxActiveChannels defaults to MaxChannels if it is not set. I don't know if you can set it in the mqs.ini file to apply to all qmgrs. |
|
| Back to top |
|
|
| tkaravind |
| Posted: Wed Dec 03, 2003 7:39 am Post subject: MAXCHANNELS/MAXACTIVECHANNELS |
|
|
Acolyte
Joined: 24 Jul 2001
Posts: 64
|
Hi vmcgloin,
Thanks for the advice ! But I still did not get what you meant by
"queue managers that have lots of client connections . . . "
Would this mean that many client connection channel definitions were created in the Q manager?
Or that even with one client connection object defined, a number of clients were trying to access the Queue manager through MQI ?
Many Thanks,
Aravind |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Dec 03, 2003 7:55 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Aravind,
When we had the error I mentioned it was with a single client connection channel but lots of clients connecting at the same time (or not disconnecting quickly enough). If you are counting up how many channels are active remenber to allow for things like SYSTEM.ADMIN.SVRCONN channels for MQExplorer connections. So it is instances of channels (rather than just definitions) that counts.
Are you getting errors or just planning ahead?
If you want to see how many channels a qmgrs has active use the runmqsc command 'dis chs(*) all'. These are a couple of extracts from a small script we used to count channels.
| Code: |
runmqsc $QMgr >$LogFile <<EOF
DIS QMGR QMNAME
*------------------------------------------------
dis chs(*) all
*------------------------------------------------
* End of script
EOF
grep -c AMQ8417 $LogFile |
Cheers,
Vicky |
|
| Back to top |
|
|
| rajmq |
| Posted: Wed Dec 10, 2003 6:00 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
I had similar problem in my production system.I think some exceptional condition my connection are not closing.I can increase max channel param also.
But when the connection are reached max level,my qmgr getting hang mode.i checked the channel status 94 connections are opened
How to close these connections, i was trying stop the channel with force mode also...but i am not able to stop.Then stop & start the QMGr it is ok.
without stop & start the QMGR!! How can i stop the above 94 connection???
Regards
raj |
|
| Back to top |
|
|
| offshore |
| Posted: Fri Dec 12, 2003 7:30 am Post subject: |
|
|
Master
Joined: 20 Jun 2002
Posts: 222
|
Sounds as though you programmers are closing the channel when they are done processing.
The application should perform the following:
MQCONN or MQCONNX
OPEN Q
CLOSE Q
MQDISC
- Sounds as though the MQDISC isn't there or not working properly.
As far a closing the channel. Once max channels are reached its tough to clear the connections out w/out a recycle of MQ. (At least in my experiences - if any has a bulletproof way I'm all ears)
If you have MQ 5.3 you can stop individual connections which really sweet.
STOP CHANNEL('CHANNEL.NAME') CONNAME('IP/HOST YOU WANT CLOSED')
There is also a few other options for the stop if the channel is stubborn and won't close.
HTH |
|
| Back to top |
|
|
|
|
