| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MAXIMUM CHANNELS REACHED |
« View previous topic :: View next topic » |
| Author |
Message
|
| r00kie |
 Posted: Mon Nov 18, 2002 4:18 am Post subject: MAXIMUM CHANNELS REACHED |
 |
|
Novice
Joined: 27 Aug 2002
Posts: 18
|
Hi,
We are running V5.2 on NT4.0 and since the upgrade we have run into MAXIMUM CHANNELS REACHED a lot. We've increased the channels from 100 to 200 then from 200 to 400 in certain instances. Does anyone know a way around this? Do we have to change the setting on all the servers?
We are also using CSD02.
Thanks,
R00kie |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Mon Nov 18, 2002 6:02 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Did you restart your QM. Any changes to qmini file takes effect only after you have restarted the QM.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| r00kie |
| Posted: Mon Nov 18, 2002 6:18 am Post subject: |
|
|
Novice
Joined: 27 Aug 2002
Posts: 18
|
Yes, we have stop/started the queue manager. We have normally done this through the MMC console remotely. Where is the QM.ini file located? Is that a better way to change this?
Thanks,
R00kie |
|
| Back to top |
|
|
| mqonnet |
| Posted: Mon Nov 18, 2002 7:12 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
On Windows platforms you dont have an explicit ini file. But everything is stored in the registry under Queuemanager Key. Check to see that it is modified.
Do you have many clients running using the same or different svrconn channel on the server side. If thats the case, then does each client appropriately terminate or disconnect when they are done what they intend to do. Becuase, if you dont, then there is a possibility that the connections are in limbo land and you try another connection while there is another active connection. Check to see if your MaxActiveChannels is set to more than the default. If it is not, then change it to say 400(if you want all the 400 to be active at the same time).
When you say that you increased the maxchannels to 400, did u issue "dis chs(*)". What did u get. Did u see 400 channels running???
Any errors in the error logs or FDc
hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| r00kie |
| Posted: Mon Nov 18, 2002 11:28 pm Post subject: |
|
|
Novice
Joined: 27 Aug 2002
Posts: 18
|
Hi again,
The error is:
18/11/02 13:42:00
AMQ9513: Maximum number of channels reached.
EXPLANATION:
The maximum number of channels that can be in use simultaneously has been
reached. The number of permitted channels is a configurable parameter in the
queue manager configuration file.
ACTION:
Wait for some of the operating channels to close. Retry the operation when some
channels are available.
As far as we can tell, the clients are not disconnecting properly and that seems to be what is causing this error. I've heard that KEEP ALIVE might be an option but the concern is that it would degrade network performance and could impact other applications that are not MQ related.
R00kie |
|
| 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
|
|
|
|
