| Author |
Message
|
| dtauzell |
 Posted: Mon Aug 26, 2002 12:54 pm Post subject: connection limit |
 |
|
Apprentice
Joined: 23 May 2002
Posts: 37
|
Hi,
Our MQ admin is out on vacation so here goes....
I have a JMS application that is creating connections against a queue manager. After creating around 100 connections I start getting 2009.
Is this a configurable limit? |
|
| Back to top |
|
 |
| boaz |
| Posted: Tue Aug 27, 2002 2:46 am Post subject: |
|
|
Apprentice
Joined: 28 May 2002
Posts: 43
|
If this is AIX, then 100 connections on one port are a limit.
(ita actually a TCP listener limit)
In this case you need another queue manager on another port and distribute the work. |
|
| Back to top |
|
|
| dtauzell |
| Posted: Tue Aug 27, 2002 5:05 am Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 37
|
We are on Solaris. I did find a setting MaxChannels that can be set in the mqs.ini file. The default is 100 so I bet this is the limit. I'll try and figure out how to change it.
Thanks for the info!
-Dave |
|
| Back to top |
|
|
| boaz |
| Posted: Tue Aug 27, 2002 6:13 am Post subject: |
|
|
Apprentice
Joined: 28 May 2002
Posts: 43
|
I dont think this is it.
A channel is a different object and this parameter means you can set up to 100 channels on the same queue manager. BUT - a queue manager is listening on a port, and here you have a limit of 100 connections on the port. So check the port limit on Sun.
Look here:
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/csqzae05/csqzae052n.htm
Table 18. Default outstanding connection requests. |
|
| Back to top |
|
|
| aadooley |
| Posted: Tue Aug 27, 2002 7:37 am Post subject: |
|
|
Newbie
Joined: 27 Aug 2002
Posts: 6
|
If you are using JNDI to connect your JMS app to the queue manager and your QCF has a TARGET set to CLIENT then a server connection channel is created (and thus a tcp connection) for each connection. This is how your MAXCHANNELS is reached. One way to fix this is to modify your qm.ini file on the Solaris box. Here's a sample:
CHANNELS:
MaxChannels = 500
MaxActiveChannels = 500
The better way (if the app is running on the same server as the qmgr) is to set your JNDI QCF TARGET setting to BIND. This (at a very high level) enables the connection to use shared memory with MQ instead of using tcp. Thus, max channels is not used. Hope this helps.
_________________
Thanx,
Alicia |
|
| Back to top |
|
|
| dtauzell |
| Posted: Tue Aug 27, 2002 7:44 am Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 37
|
Thanks for the information. Our JMS client will be on a different machine so we'll need to use CLIENT instead of bind.
Perhaps we should setup an mq server on the JMS client box and configure remote queues on it?
-Dave |
|
| Back to top |
|
|
| aadooley |
| Posted: Tue Aug 27, 2002 8:53 am Post subject: |
|
|
Newbie
Joined: 27 Aug 2002
Posts: 6
|
This depends on the design of your app and the number of users trying to connect to it.
_________________
Thanx,
Alicia |
|
| Back to top |
|
|
|
|
