|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Maximum connections and Maximum channels |
« View previous topic :: View next topic » |
Author |
Message
|
pshan81 |
Posted: Fri Dec 03, 2010 3:00 am Post subject: Maximum connections and Maximum channels |
|
|
Acolyte
Joined: 24 May 2005 Posts: 72
|
We used to get MAX_CONNS_LIMIT_REACHED (mqrc 2025) and Maximum channels reached error in production. Search on web asks to change MaxChannels on qm.ini.
My view is both are different. Maximum number of channels error is thrown when the configured max channel count (SDR, RCVR, SVRCONN etc) threshold is reached. The error will not be thrown if applications use bindings mode and channels are within limit.
Max connection limit error is thrown when the configured handles for the queue manager threshold is reached. This will be thrown even for binding connections.
Please provide your views. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Dec 03, 2010 5:39 am Post subject: Re: Maximum connections and Maximum channels |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
pshan81 wrote: |
Max connection limit error is thrown when the configured handles for the queue manager threshold is reached. This will be thrown even for binding connections.
Please provide your views. |
Binding connections don't use channels. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
pshan81 |
Posted: Mon Dec 06, 2010 3:17 am Post subject: |
|
|
Acolyte
Joined: 24 May 2005 Posts: 72
|
Yes Vitor. I agree.
But what I am claiming is Max_CONNS_LIMIT_REACHED will be thrown only for bindings and the reason is the handles reached the threshold configured in the qmgr MAXHANDS attribute. |
|
Back to top |
|
 |
jeevan |
Posted: Mon Dec 06, 2010 5:53 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005 Posts: 1432
|
pshan81 wrote: |
Yes Vitor. I agree.
But what I am claiming is Max_CONNS_LIMIT_REACHED will be thrown only for bindings and the reason is the handles reached the threshold configured in the qmgr MAXHANDS attribute. |
I think either the binding connection takes the handles. If it was so, the error message should be max handles reached not max conneciotn reached.
MAXHANDS refers to the maximum number of objects that a single connection can have open at the same time. So, if an application thread issues an MQOPEN for a queue, that counts as 1, and so on for each queue that is opened in that thread. A separate thread in the same or in a different process also has its own MAXHANDLES objects that it can open. The total number of handles for a queue, for example the number of applications that have a queue open, is not related to MAXHANDLES.
Source: http://www-01.ibm.com/support/docview.wss?uid=swg21174674 |
|
Back to top |
|
 |
gbaddeley |
Posted: Mon Dec 06, 2010 2:27 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
pshan81 wrote: |
But what I am claiming is Max_CONNS_LIMIT_REACHED will be thrown only for bindings and the reason is the handles reached the threshold configured in the qmgr MAXHANDS attribute. |
RTFM.
Reason Code 2025 MQRC_MAX_CONNS_LIMIT_REACHED is unrelated MAXHANDS.
Reason Code 2025 can occur for any type of connection (binding or client). It relates to the total number of concurrent MQ connections that all programs have made to a Queue Manager, or via a Java Connection Manager.
Reason Code 2017 MQRC_HANDLE_NOT_AVAILABLE occurs if a process reaches the MAXHANDS limit (the maximum number of MQ object handles that a *single process* can have open on a Queue Manager).
Both of these usually indicate an application design error or a programming error, or MQ capacity planning has not been done correctly. _________________ Glenn |
|
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
|
|
|
|