| Author |
Message
|
| patrik |
 Posted: Tue Nov 02, 2004 2:03 am Post subject: two qmgrs with the same name |
 |
|
Newbie
Joined: 02 Nov 2004
Posts: 1
|
we are cloning a qmgr to a new server. these two qmgr's have the same name. now we want to send messages via a remoteq to the new qmgr. is that a problem because the target qmgr name is the same as the source qmgr?
thanks, patrik |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Tue Nov 02, 2004 5:30 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Nov 02, 2004 9:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Is it technically possible to send a message from QM1 on ServerA to QM1 on ServerB? Yes.
Would you want 2 servers in your system with the same QM name? NO!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| javagate |
| Posted: Tue Nov 16, 2004 2:49 pm Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
per MQSeries doc you should not have the more then one queue-manager with the same name with in a network. the problem you will run into will be sync problems with your channels.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Nov 16, 2004 3:52 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| javagate wrote: |
| per MQSeries doc you should not have the more then one queue-manager with the same name with in a network. the problem you will run into will be sync problems with your channels. |
Yeah, and that is just the beginning of the problems you will face having two active MQManagers on the same network with the same name.
"PULL UP! PULLLLLLLLLLL UUUUUUUP!"
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Nov 16, 2004 4:42 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| per MQSeries doc you should not have the more then one queue-manager with the same name with in a network |
This is only documented for Clusters. However, it is recommended that you don't do it.
Moreover, if you are not Clustering, then it is just a matter of being very careful about how you connect to QMs and how you inter-connect QMs. It will not cause MQ problems
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| javagate |
| Posted: Tue Nov 16, 2004 4:50 pm Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
I am sorry you are incorrect. It is documented as stated.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Nov 16, 2004 6:01 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Actually I do have two MQManager with the same name on my network but one of them is on a Disaster Recovery Server. It was set up this way when I started here. Personally I would have done it differently but....
The only time I start this Twin is to populate objects that I have created on the Prod MQManager and during Disaster Recovery Tests.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
|
|
