Author |
Message
|
Mallik |
Posted: Wed Mar 10, 2004 9:46 am Post subject: 2 QMGRs on a Single Production box |
|
|
Acolyte
Joined: 29 Feb 2004 Posts: 53
|
I would like to know some experts suggestions on having 2 QMGRs on a single production box for 2 different applications.
We have some strict restrictions on hardware. The box we are looking at is Solaris with 2 CPU & 4GB memory. And the expected traffic for each QM is around 15000msgs/Hr (could be higher that that).
can some one let me know the factors that we need to consider before we decide to have 2 QMGRs on a single box.
Thanks
MQ Guy |
|
Back to top |
|
 |
csmith28 |
Posted: Wed Mar 10, 2004 11:21 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
While it is eminently possible to have multiple MQManagers on the same server it is my experience that you will be better of just having the new application use the existing MQManager.
Most of the time on Severs with more than one MQManagers if one Manager gets so bad that it stops responding it will impact the other MQManagers on that server in much the same way.
Often if one MQManager Fails even if it does'nt impact the other MQManager you will not be able to restart the failed MQManager do to the lingering Shared Memory Segments and Semaphores that orphaned when the MQManager went down.
The problem here is that you cant use the ipcrm command to free up those resources because there is no way of telling what Shared Memory Segments and Semaphores belong to what MQManager. So to restart the failed MQManager you have to stop the one that didn't fail then clean up the Shared Memory Segments and Semaphores and start both back up. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
vennela |
Posted: Wed Mar 10, 2004 11:30 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
Often if one MQManager Fails even if it does'nt impact the other MQManager you will not be able to restart the failed MQManager do to the lingering Shared Memory Segments and Semaphores that orphaned when the MQManager went down. |
Though I have never tried I thought amqiclen would ipcrm the resources of only a particular QMGR without affecting other QMGRs on the box |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Mar 10, 2004 1:27 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
csmith,
I have to disagree here.
depending on your setup it can be wise to have multiple Queuemanagers.
for example when in the near future the application need be moved, not changes will be required as you move the application with it.
Another situation is where you have a lot of clients connecting, somehow this can cause a problem now and then and you will be able to shut down just that queuemanager and not affecting other connections (like to the 'outside' world or to your broker running on another queuemanager)
there are many more situations that can be thought of.
vennela is right amqiclen (with proper parameters supplied) can kill the share memory of a particular Queuemanager. _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
csmith28 |
Posted: Wed Mar 10, 2004 2:33 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
@vennela
amqiclen don't work so good even on Servers that have only one MQManager it will fail to kill all the Shared Memory Segments and Semaphores. It usually leaves two. I was real excited when they introduced it but went back to the more reliable ipcs | grep mqm.
I actually wrote my own script call ipcrmall. It works great but does not distinquish between MQManagers.
@MichaelDag
Disagreeing is what forums are for.
None of the scenarios you spoke of were suggested in the post that started this thread.
Two apps, one server roughly 15000 msgs/hour. One MQManager should be able to handle that just fine.
Currently on one of my production servers (AIX 4.3.3, MQ5.3.0.4) I have 668 SVRCONN channels running on one MQManager serving 14 applications. I haven't had any outages for the last year in which the MQManager o r any part there of could be blamed.
There are pro's and con's to having multiple MQManagers on a single server and I don't personally advocate that under most circumstances but I have done it and I posted some of the problems that I encounter as a result. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Mar 10, 2004 2:51 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
csmith28 wrote: |
Disagreeing is what forums are for. |
Yup
csmith28 wrote: |
None of the scenarios you spoke of were suggested in the post that started this thread. |
True!
csmith28 wrote: |
Two apps, one server roughly 15000 msgs/hour. One MQManager should be able to handle that just fine.
|
Agree, as I didn't think the volume was a problem I thought of other reasons not to 'share' the QueueManager. _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
Mallik |
Posted: Thu Mar 11, 2004 11:24 am Post subject: 2 QMGRs on a Single Production box |
|
|
Acolyte
Joined: 29 Feb 2004 Posts: 53
|
Thanks for your valuable suggestions... |
|
Back to top |
|
 |
vennela |
Posted: Thu Mar 11, 2004 11:31 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
I was real excited when they introduced it but went back to the more reliable ipcs | grep mqm.
|
Is that the reason I don't see the command in the Sys Admin manual. I am 95% sure that it was documented in the Sys Admin manual but in the recent manuals I can't find it. Did they pull it out or is my memory not serving me right. |
|
Back to top |
|
 |
csmith28 |
Posted: Thu Mar 11, 2004 12:05 pm Post subject: @ven |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
I'm not sure. Like I said, I haven't spent much time with it since the initial dissapointment. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
bower5932 |
Posted: Thu Mar 11, 2004 1:18 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
I didn't think you were supposed to run the command unless directed to by IBM Support. Because of this, I didn't think that it was actually documented. However, it shows up often enough on the listserver and various newsgroups that people know about it. |
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Mar 11, 2004 1:25 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
so when directed by IBM to run the command, does it work as intended or not??? _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
csmith28 |
Posted: Thu Mar 11, 2004 2:15 pm Post subject: QM |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Well being the bold type of admin that I am I played around with it on some of my LAB Servers. In almost every instance that I ran amqiclen after forcing an ungraceful failure of the MQManager it would fail to clean up all the Memory Segments and Semaphores even though I had killed all the MQSerie processes.
That was just with one MQManager running.
I never really tried building a second MQManager and forcing one them to fail. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Mar 11, 2004 2:26 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
|