| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS subscriber issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| smeunier |
 Posted: Wed Nov 01, 2006 1:37 pm Post subject: JMS subscriber issue |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
Two are Brokers joined in a collective(BRK A, BRK B).
One publisher on BRK A
One consumer on BRK A (receives messages)
One consumer on BRK B (Does not receive messages)
Subscriber on BRK B does not receive messages.
This is Websphere V6 Message Broker. Publications are via a Message Flow (From JMS Publisher) using the Publication Node.
Subscription list shows subscriber on both Brokers, and the brokers are subscribers as well. Yet I can only get messages deliver to the Broker on which they were published.
Issueing a:
mqsireportproperties BRKDTEMQHUB1 -e default -o
DynamicSubscriptionEngine -r
Partial results: I'm curious about the test in Red. Is this what is causing the Publication to not go to BRKR B? This has become a very perplexing problem.
clientId='mqrfh2:DTEMQHUB2:SYSTEM.BROKER.IPC.QUEUE.839888.20061005000919
86:T'
user='mqbrkr'
subscriptionPoint=''
filter=''
persistent='false'
localOnly='true'
pubOnReqOnly='false' |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Nov 01, 2006 9:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you specify a local publication only it will not be published in the collective. You should specify a global publication for that to happen.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smeunier |
| Posted: Thu Nov 02, 2006 11:09 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
| I would love to, but for the life of me cannot find documentation or class methods that allow this to be set. Can you enlighten me? It would seem that global publication would be the default, not the exception. At this point, I feel like I need to intercept the publication message and set it in the RFH2 Header, as i cann not see how to do it via JMS. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 02, 2006 4:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| smeunier wrote: |
| I would love to, but for the life of me cannot find documentation or class methods that allow this to be set. Can you enlighten me? It would seem that global publication would be the default, not the exception. At this point, I feel like I need to intercept the publication message and set it in the RFH2 Header, as i cann not see how to do it via JMS. |
It's all in the psc folder of the RFH2.
Read up and experiment. RFHUTIL and the debugger are your friends...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smeunier |
| Posted: Thu Nov 02, 2006 6:51 pm Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
Yes, I have seen the option on RFHUTIL and have used the debugger to look at the incoming RFH2.
It still doesn't make since that I would need to set this to: localOnly=false to have it globably published to all subscribers on all domains. This seems like it should be a default action of the broker.
Thanks for the info. |
|
| 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
|
|
|
|
