| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| v7 pubsub issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jcv |
 Posted: Wed Nov 19, 2008 2:29 am Post subject: v7 pubsub issue |
 |
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
Hello,
I think that maybe pubsub related issues deserve their own forum.
I'm testing v7 using clusters for distributed pubsub. Cluster is working well, clustered topics once defined become visible immediately in all repositories. I can't understand why publications don't reach all subscribers.
I have 3 qmgrs, and I have defined clustered topics on each. I'm using options "Test Publication..." and "Test Subscription..." under "Topics" in qmgrs tree of MQ Explorer. Topics are defined with all possible options set to all (pubscope, subscope, all messages P and NP delivery set "To all subscribers"...). I'm subscribing and publishing on all 3 qmgrs. I think I see this behaviour.
1. It doesn't matter where the topic is physically defined, local subscriber always gets the publication.
2. Subscriber on one qmgr (QMA) always gets the publication, the "third" qmgr subscriber, that is, not QMA, and not the one on which publisher connects, never gets the publication. I don't see what's special about QMA, it is one of the FR, but not the only one among theese 3 qmgrs. And it's not the qmgr on which topic is defined.
I'm checking messages count on several places. One is under "Subscriptions", option "Status..." on each qmgr, and on qmgr where the topic is defined "Topic Status - Subscribers..." under the observed topic. The last one shows that message is sent to all subscribers, while the first three show message count according to what I see from the subscriber window (two have received and one is not).
I suppose, there is no problem with topic selectors, since all subscriptions are registered on the topic. I'm also checking clussdr channel status and it shows me that after publishing, messages are sent to both remote destinations. Subscription properties are on all qmgrs:
Destination class: Managed
Destination name: SYSTEM.MANAGED.NDURABLE.etc...
Durable: NO
. . .
I don't see any messages in SYSTEM.DEAD.LETTER.QUEUE. Anyone has idea at glance where did I go wrong?
My another idea is to try qmgr hierarchy, but I don't see why does that not work with cluster. |
|
| Back to top |
|
 |
| jcv |
| Posted: Wed Nov 19, 2008 2:48 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
Another idea is to add another qmgr to cluster and see what will happen.
When I said that message count was incremented for all subscriptions, that was when I published from the qmgr where the topic was defined. I did tests publishing from all qmgrs as I said, but didn't check that count, and now I have some problems preventing me from doing that, at the moment. |
|
| Back to top |
|
|
| jcv |
| Posted: Wed Nov 19, 2008 10:42 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| I have solved this problem in the most simple way which always works in similar situations. It helped me a lot when I saw what happened when I added another qmgr to the cluster, as PR. It received information about clustered topics which no longer existed. Hence, I was looking at 2 FR's and 1 PR not having this obsolete objects displayed and this new one who had. When I refreshed the cluster on that new PR, it's repository was cleared, but as soon as I did a change in an existing clustered topic, that change propagated to all repositories, plus, obsolete topics reappeared in new PR again. |
|
| 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
|
|
|
|
