| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Only one topic selected for remote subscription. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cogito-Ergo-Sum |
 Posted: Wed Apr 27, 2011 3:31 am Post subject: Only one topic selected for remote subscription. |
 |
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
On Linux, I have two queue managers, QM01 and QM02. On QM01, I am having four topics with topic strings as a/b/p, a/b/q, a/b/r and a/b/s. Also, on QM01, I have a subscription for topic a/b/# (Topic level wild-card) whose destination queue manager is QM01 and destination is a local queue (QM01.Q01). I have another subscription for topic a/b/# (Topic level wild-card) on QM01 whose destination queue manager is QM02 and destination is a local queue (QM02.Q01) on QM02.
I publish to all of the topic strings mentioned above and receive all of them in QM01.Q01. However, on QM02.Q01, I see only a/b/r. All the publications are done in exactly the same way with Q program. I am not sure, why publications for only this particular topic are seen.
What am I doing wrong ?
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
 |
| shashikanth_in |
| Posted: Wed Apr 27, 2011 7:31 pm Post subject: |
|
|
Centurion
Joined: 26 Feb 2009
Posts: 123
|
What level of MQ are you using? MQ v7?
I believe you have a subscription at QM02 for "a/b/#" which flows to QM01 as both queue managers are in a hierarchy or cluster. If you are using MQ v7 have you tried samples? |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Apr 27, 2011 7:36 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Yes, MQ is at v7.
There are no subscriptions at QM02. They exist only at QM01. But, one of the subscriptions has destination queue manager as QM02 and destination name as that of a queue local at QM02.
The queue managers are not in a hierarchy or a cluster.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 27, 2011 7:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Basically you are missing topics a/b/p and a/b/s on QM02.
Check exactly using the display sub command what the subscription for QM02 is. If it truly is a/b/# and the wildcard character is set to topic and you can prove that nobody is consuming the missing messages, you need to open a PMR... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Apr 27, 2011 10:04 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| fjb_saper wrote: |
Basically you are missing topics a/b/p and a/b/s on QM02.
Check exactly using the display sub command what the subscription for QM02 is. If it truly is a/b/# and the wildcard character is set to topic and you can prove that nobody is consuming the missing messages, you need to open a PMR... |
As I mentioned before, I do not have a SUB definition in QM02. All the SUB definitions are on QM01 where one of them has a destination manager as QM02.
I have checked again with DISPLAY SUB commands and can confirm that the definitions are correct. Also, WSCHEMA is set to TOPIC.
Here is one another observation that I have not understood. For a subscription, if the DEST parameter is just a queue name, then why cannot I just mention a remote queue definition to allow 'external' subscription ? When I attempted, the publication goes fine, but, there is no message in the queue of the other manager. I have read the appropriate parts of Intercommunication and PubSub guides. But, I do not see anything supportive or contrary.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 27, 2011 11:15 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Cogito-Ergo-Sum wrote: |
| ...Here is one another observation that I have not understood. For a subscription, if the DEST parameter is just a queue name, then why cannot I just mention a remote queue definition to allow 'external' subscription ? When I attempted, the publication goes fine, but, there is no message in the queue of the other manager... |
Have you checked the transmission queue? Is the channel running? Have you checked the DLQ on QM02?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Apr 27, 2011 11:55 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| exerk wrote: |
| Have you checked the transmission queue? Is the channel running? Have you checked the DLQ on QM02? |
Transmission queue ok.
Channel was NOT running. My bad.  I might have altered values and stopped it when I was trying the original scenario as mentioned in my first post.
So, I got the channel running and published. The DLQ had the messages.
A bulb went on over me. Could it be that the queue length was short due to which messages were rejected ? That is right ! Changed the length and now everything is working with remote queues.  For the scenario mentioned in the original post, it should work too; but, first a victory dance. 
Thank you, all for your support !
(Also, apologies for not trying harder before posting.)
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| shashikanth_in |
| Posted: Thu Apr 28, 2011 7:24 pm Post subject: |
|
|
Centurion
Joined: 26 Feb 2009
Posts: 123
|
| Something I did not understand: If the channel between QM01 and QM02 was not running how did the publications of only a/b/r reached QM02.Q01? |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Thu Apr 28, 2011 7:42 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| shashikanth_in wrote: |
| Something I did not understand: If the channel between QM01 and QM02 was not running how did the publications of only a/b/r reached QM02.Q01? |
The channel was running with XMITQ Q1 initially for the first scenario. Then, for the second scenario (remote queue), I had changed the XMITQ name. After doing that, I had forgotten to start the channel.
As I had mentioned earlier, with remote queues, nothing was getting transmitted. When I did get the channel running (with correct XMITQ name), messages were getting transmitted for a/b/r only. When I checked the DLQ, I had a thought about the queue lengths. That resolved the problem.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| 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
|
|
|
|
