| Author |
Message
|
| eva555 |
 Posted: Tue Sep 24, 2013 8:32 pm Post subject: Duplicate queue manager names |
 |
|
Novice
Joined: 10 Sep 2012
Posts: 15
|
I know its a very bad idea to have duplicate qmgr names in a network. But we have an unavoidable situation in qmgr migration.
Only half of the applications would be connecting to the migrated qmgr and other half needs to connect to the old qmgr. And both qmgr needs to be with the same name. Its a DQM set up and both the old and migrated server are not sharing a VIP.
Will this still cause issues in message flows? |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Sep 24, 2013 10:55 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Are these queue managers going to be in a cluster? If so, bad idea! If not, why the necessity to have the same name - hard-coded in the apps perchance?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| eva555 |
| Posted: Wed Sep 25, 2013 1:06 am Post subject: |
|
|
Novice
Joined: 10 Sep 2012
Posts: 15
|
They are not in clusters.
Actually its an old interface and we are not sure how many and how they connect to the qmgr. The known interface we migrate and rest are to connect to the old qmgr... But all of these qmgrs are NOT part of any MQ clusters. Its totally a distributed queueing |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 25, 2013 4:47 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| eva555 wrote: |
| Actually its an old interface and we are not sure how many and how they connect to the qmgr. The known interface we migrate and rest are to connect to the old qmgr... But all of these qmgrs are NOT part of any MQ clusters. Its totally a distributed queueing |
So find out how they are connected. If it's hard coded you've been painted into a corner; if not, use a new name for your queue manager.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| queuemanager |
| Posted: Wed Sep 25, 2013 4:47 am Post subject: |
|
|
Apprentice
Joined: 28 Nov 2006
Posts: 43
Location: Bangalore
|
| Technically there are no issues if the VIPs/PORT are going to be different but operationally you may have difficulties while deciding which server to logon and check the issue. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 25, 2013 4:52 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| queuemanager wrote: |
| Technically there are no issues if the VIPs/PORT are going to be different but operationally you may have difficulties while deciding which server to logon and check the issue. |
And you have hit the nail squarely on the head...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| rcp_mq |
| Posted: Wed Sep 25, 2013 6:58 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
Would you consider an alias queue manager, if you can't reconcile hard coding?
(Just a thought) |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 25, 2013 9:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| rcp_mq wrote: |
Would you consider an alias queue manager, if you can't reconcile hard coding?
(Just a thought) |
If the apps bind there's no way to 'fool' the app with a different name, and if the apps are client and passing a specific name that's been hard-coded then same thing. Queue manager aliases are more an internal routing/rerouting mechanism.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
