| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Guidelines of how many Qmgrs per machine |
« View previous topic :: View next topic » |
| Author |
Message
|
| gforster |
 Posted: Tue May 22, 2001 2:52 am Post subject: |
 |
|
Newbie
Joined: 21 May 2001
Posts: 1
Location: Consignia, Berkshire, UK
|
Are there any guidelines on how many queue managers can be run on a machine?
In relation to this, what needs to be monitored on NT and HP-UX machines to determine the impact of MQSeries on a machine?
Gareth |
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue May 22, 2001 10:39 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
From what I know, at least on UNIX platforms, there is no limit to the number of queue managers; you are only limited by the hardware. As you may know (it's described in another post below) the Solaris kernel configuration needs to be altered to support MQSeries. Heavy load or additional queue managers could further rachet these values up. At some point, the soft limits you set will equal the hard limits, and eventually reach the system's limits. So the number of queue managers possible is governed by a large number of dynamic factors, but as I said, MQSeries won't stop you from running as many queue managers as the platform can support
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| ChrisW |
| Posted: Wed May 23, 2001 12:34 am Post subject: |
|
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
| A slightly different question - By having several Queue Managers running on UNIX, as long as you keep their /var/mqm/qmgrs/xxx and logs seperate and so don't run out of disk space, is there anything that can happen to one Queue Manager that will affect the others eg shared memory? |
|
| Back to top |
|
|
| anantha |
| Posted: Tue Sep 18, 2001 5:49 am Post subject: |
|
|
Newbie
Joined: 04 Sep 2001
Posts: 7
|
If we have multiple QManagers on a single machine, The first thing to do is not to define any one as default QManager. If done, this will be a common source of error, selecting the wrong QManager. As far as the effect of shared memory is concerned, If one of the QManagers needs to be stopped manually, care to be taken to identify and release/stop only those shared memory and processes of the problem QManager.
Ananth
Thanks
Ananth |
|
| Back to top |
|
|
| pal |
| Posted: Tue Sep 18, 2001 11:54 am Post subject: |
|
|
Apprentice
Joined: 14 Aug 2001
Posts: 35
|
Re:space, each QMgr preallocates space at creation time so you should not run into the problem of one interfering with anothers space.
File system space allocation should be carefully considered for a network of QMgrs. |
|
| Back to top |
|
|
| kolban |
| Posted: Tue Sep 18, 2001 2:42 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| If you want multiple queue managers on a Unix based machine and create separate log and queue file systems, I believe you can run into serious problems. At least on MQ 5.1, some of the shared memory components used Unix file i-node values as keys. These are unique ... within the same file system. The moment you add more file systems, the unqique ness is lost. |
|
| 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
|
|
|
|
