| Author |
Message
|
| KIT_INC |
 Posted: Wed Nov 08, 2006 8:46 pm Post subject: Pub not working |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| I have pub/sub running on WMQI v21 with MQ53. Existing subscribers using MQ works fine. A new subscriber subscribing to the same topic from a WMQ V6 system using JMS never receive the publication. The only thing I noticed under the subscription window of the WMQI control center is all existing subscription has mqrfh2 , the new JMS subscriber has mqrfh. Is this the reason ? The JMS subscriber is a new client who claim that the JMS program has no problem getting the subscription from their WMB V6 broker. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Nov 08, 2006 9:49 pm Post subject: Re: Pub not working |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| KIT_INC wrote: |
| The JMS subscriber is a new client who claim that the JMS program has no problem getting the subscription from their WMB V6 broker. |
Don't know how you do subscriptions in 2.1 but in V6 the easiest way is to post to a speicific queue provided by the subscriber. The subscriber can then just listen to the queue and consume whatever comes along.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 09, 2006 2:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, the base Broker in WMQ uses MQRFH headers and the Broker in WMB uses the MQRFH2 header.
There's a property on the TCF that controls what version of the Broker is being used - and thus which header is being produced. I forget what it is.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 09, 2006 3:43 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
Yes, the base Broker in WMQ uses MQRFH headers and the Broker in WMB uses the MQRFH2 header.
There's a property on the TCF that controls what version of the Broker is being used - and thus which header is being produced. I forget what it is. |
I thought it was the version property set to 1 or 2
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 09, 2006 4:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm pretty sure it's the Version property - but I haven't double-checked. So.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Thu Nov 09, 2006 5:36 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Thanks for the quick response. Change brokerver of TCF to V2 fix the problem. It now shows mqrfh2 for the new subscriber.
However my client confirmed that they have brokerver(v1) in their TCF and it works with their WMB V6 broker. I was under the impression that WMQI V21 supports mqrfh also. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 09, 2006 5:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It is a new feature in v6 of Message Broker that the default MQ broker can participate in the same Pub/Sub topologies.
It should not be extremely surprising that a new version of a product is more flexible than an out of service version of a product.
Please upgrade from 2.1.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
