| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| failed to deploy configuration for broker collective |
« View previous topic :: View next topic » |
| Author |
Message
|
| glacier_huang |
 Posted: Wed Nov 28, 2007 3:41 am Post subject: failed to deploy configuration for broker collective |
 |
|
Newbie
Joined: 26 Nov 2007
Posts: 2
|
Issue about JMS Pub/Sub using MB broker collective. Please help me out.
Here is my scenario:
I have two brokers BROKER1 and BROKER2.
BROKER1 and ConfigManager running on queue manager QM1
BROKER2 is running on QM2
I have rcreated sender and receiver channel pair on both queue managers and they are working fine( because i am able to deply BROKER2 to Configmanager)
I have created a collective between the two brokers(by Double cliking on broker topoloy ->select collective-> create connection betwwen brokers and save it).
i have the same message flows deploying to BROKER1 and BROKER2.
Then I run a Publisher on Broker1 and a Subscriber on Broker2 on a certain topic.
I can see the subscription from Broker2.
But I can't see the subscription to the same topic from Broker1 with Client being like mqrfh2: QM2:SYSTEM.BROKER.INTERBROKER.QUEUE.* as expected.
and Subscriber@Broker2 can't receive message from Publisher@Broker1
And when I try to fix it, I find out it is probably because the Broker Topology is not deployed, which I can verify from CMP API Excerciser where the isDeployed() is false.
So, I try to deploy using WMB Toolkit, and get a error with code 2086. Also I try to use the "mqsideploy" command, it doesn't work.
Also I try to Cancel Deployment and redo deployment ,it doesn't work either. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 28, 2007 3:46 am Post subject: Re: failed to deploy configuration for broker collective |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| glacier_huang wrote: |
| So, I try to deploy using WMB Toolkit, and get a error with code 2086. |
| Code: |
| 2086 0x00000826 MQRC_UNKNOWN_OBJECT_Q_MGR |
I'd double check all the comms for a start, and make sure you have name resolution working.
I'd also double check your BROKER1 is entirely clear about the name of the queue manager it's running on (as with a comms issue I'd have really expected an unknown remote q mgr error).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 28, 2007 3:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Do you have connection between BROKER1 and BROKER2 qmgrs?
Are you sure you're registering the subscription with the right broker, as per how collectives work?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| glacier_huang |
| Posted: Wed Nov 28, 2007 6:26 pm Post subject: |
|
|
Newbie
Joined: 26 Nov 2007
Posts: 2
|
After I deleted ninactive broker in the topology and redploy, and it is done with no errors.
However, here is another issue:
I run myPublisher and mySubscriber on both Broker1 and Broker2, then have them publish and subscribe on the same topic.
mySubscriber@Broker1 can receive message from myPublisher@Broker2,
but mySubscriber@Broker2 can not receive message from myPublisher@Broker1.
I check the SYSTEM.BROKER.INTERBROKER.QUEUE.1T of the Queue Manager on which Broker2 runs, and there are the messages from Broker1.
Do anybody know why? |
|
| 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
|
|
|
|
