| Author |
Message
|
| kishoreraju |
 Posted: Mon Mar 20, 2006 6:13 am Post subject: Publish subscribe collective problem. |
 |
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
Hi the below is my present environment set up.
I have two brokers BROKER1 and BROKER 2.
my 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 reated a topic and added to public groups.
i have two flows one for publish running on BROKER1 and another is subscrible flow which is running on BROKER2 .
i am able to see the subsciption message that send to the broker for the topic in subscription list(Brokertopology->subscriptions-query)
but i am not able to get the published message on the topic form broker one into the queue which is QM2 that i have given in the subscription message.
can any one tell wht exeactly i am missing and where it went wrong. |
|
| Back to top |
|
 |
| kishoreraju |
| Posted: Mon Mar 20, 2006 11:59 pm Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
The below is exception that i am getting whne i am publishing a message.
( BRK2.default ) Message (of type 'SYSTEM.BROKER.INTERBROKER.QUEUE') on incorrect queue 'Message on incorrect queue'.
An application put a message of type 'SYSTEM.BROKER.INTERBROKER.QUEUE' on queue 'Message on incorrect queue'. This queue is not intended for messages of that type and the message was not processed.
Ensure that your applications are putting messages on the correct queue. Publish and Delete Publication messages should only be put on application queues. Control messages should only be put on SYSTEM.BROKER.CONTROL.QUEUE. Correct the application, then retry the operation. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 21, 2006 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
How are you publishing the message? Are you using a publication node?
Or are you trying to directly publish to SYSTEM.BROKER.INTERBROKER.QUEUE?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreraju |
| Posted: Tue Mar 21, 2006 10:46 pm Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
| I am using publication node to publish a message |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 22, 2006 6:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay. So hopefully the problem is not with the publication.
How are you registering the subscription? Are you registering it to broker1 or broker2?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreraju |
| Posted: Sat Mar 25, 2006 4:25 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
| I am Publishing the Message using Broker1 and i am using broker2 for subscription |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 25, 2006 6:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are you sure that's the full error message you're getting? Because that text is very confused.
Okay, so you have configured broker 1 and broker 2 in a collective. You have successfully deployed the collective topology.
You deployed a flow to broker 1 that is using a publication node to create messages.
You then manually or otherwise registered a subscription with broker 2 for the topic, and specified a reply to queue on broker 2's qmgr.
And you are not able to publish messages this way?
It's probably worth opening a PMR. And try using broker tracing to get a better idea of what's going on.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| csdenis |
| Posted: Fri Aug 11, 2006 3:58 am Post subject: |
|
|
Novice
Joined: 06 Oct 2002
Posts: 24
|
Hi,
I got a similiar problem here. I use BROKER1 (using QM1) to publish (by publication node). BROKER2 (using QM2) to subscribe. Both broker belongs to the same collective and using the same ConfigMgr.
Broker2 receives the message, but it is in SYSTEM.BROKER.INTERBROKER.QUEUE.1T instead of the subscription queue i specify. And i can see that it stays in the queue as a backout message.
Also, the broker creates the following entry in the subscription list
"User" Field = 'system',
"Broker" Field = 'BROKER1'
"Client" Field = 'mqrfh2:QM2:SYSTEM.BROKER.INTERBROKER.QUEUE.1'
--> Not sure why would this happen and is it a normal behaviour?
Any suggestions? Thanks in advance. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 11, 2006 1:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
It just means that broker QM2 subscribed @ QM1 to the topic and is expecting to pick up the messages thus published in SYSTEM.BROKER.INTERBROKER.QUEUE.1 to publish them himself to the right subscribers.
Isn't that the expected behavior in the collective?
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| csdenis |
| Posted: Fri Aug 11, 2006 5:41 pm Post subject: |
|
|
Novice
Joined: 06 Oct 2002
Posts: 24
|
thank you for your reply, sorry if my question is really dumb,
but in this case, how can i get the message to my target queue in QM2? am i suppose to get the message from SYSTEM.BROKER.INTERBROKER.QUEUE.1 of QM2 or is there anyway to make the message goes into my target queue in QM2 directly without passing the SYSTEM.BROKER.INTERBROKER.QUEUE.1 ?
Thanks |
|
| Back to top |
|
|
|
|
