| Author |
Message
|
| vishBroker |
 Posted: Tue Jan 15, 2013 8:46 am Post subject: One of the clustered QM, not receiving publications |
 |
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Hi,
I have 4 QMs clustered.
QM1 and QM3 have full repository.
I am subscribing to topicString 'MBC/01' on all the 4 QMs.
{Subscribers Sub1 on QM1, Sub2 on QM2, Sub3 on QM3 and Sub4 on QM4.
They all subscribe to 'MBC/01' topic String. }
The published message is being received by QM1,QM2 and QM4 but it is NOT being received by QM3.
I publish message on QM1.
MQ Version - 7.0.1
OS - windows (MS server 2003) (Dev environment)
The scope of subscription is ALL.
I compared the subscription on QM3 (which is NOT working) with other subscriptions(which are working for SAME topic string. )- the only difference I see is SUBID and correlID, creation and alteration dates - which is obvious. (using explorer)
What I mean to say is - all the 4 the subscribers have SAME properties e.g. SCOPE, durability,topicString,subscriptionLevel.
The cluster channel definition on problematic QM(QM3) are also fine I guess. Because when I tried giving destinationQM = QM3 and destination Name=Q1 on QM3 for subscriber subscribed on QM1, I can see that message is published successfully and stored in the destination queue. So communication to QM3 from other clustered queues is FINE.
Kindly help me in understanding, what I am missing? What I need to do so that subscribers on QM3 gets publication like other clustered QMs.
FYI - I am using DataPower to publish messages with topicString 'MBC/01' on QM1.
Regards,
Vishnu. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jan 15, 2013 8:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you use the sample publisher application connecting to QM1 and publish to the same topic, do you see the same failure, or is the message received by all qmgrs?
It's not clear from what you've said if you tried that or not.
Do you otherwise see messages on a DLQ somewhere or stuck on a transmit queue?
Do you observe errors in the logs on any of the qmgrs? |
|
| Back to top |
|
|
| vishBroker |
| Posted: Tue Jan 15, 2013 11:29 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Thanks for the response.
I HAVE done following testing.
All the testing is from same application (dataPower-xi50)
I am publishing to same topic string 'MBC/01'
4 QMs are clustered with Full repository on QM1 and QM3.
4 subscribers - subscribing to same topic with scope=ALL. All are durable.
Case -1 .
Publish message with topicString 'MBC/01' to QM1.
Result - Message is received by QM1,QM2 and QM4 subscribers. QM3 DOES NOT receive message
Case-2
Publish message with same topicstr to QM2
Result - Message is received by QM1,QM2 and QM4 subscribers. QM# DOES NOT receive message
Case-3
Publish message with same topicstr to QM3
Result - Message is received by ALL queue Managers, including QM3
I checked the errors on QM3 - but did not find any meaningful error.
I am looking at '%mqDir%\qmgrs\QM3\errors' . Should I look at something else.
I checked other clustered QMs also. Did not find any error.
Kindly suggest. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 15, 2013 11:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| vishBroker wrote: |
Thanks for the response.
I HAVE done following testing.
All the testing is from same application (dataPower-xi50) |
Try testing from the MQ sample application from a non-datapower machine.
You are looking at the right log files.
You should also look at the dead letter queue and the cluster transmission queue - at a minimum on QM1, ideally on QM1 and QM2. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Tue Jan 15, 2013 11:40 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
As per my little understanding, it seems - the subscriptions on QM3 are NOT being proxied on other QMs.
Well, I checked system queues - found a message on 'SYSTEM.DURABLE.SUBSCRIBER.QUEUE' - with data as NOTs - that is something, I DID NOT published. Just wanted to share.
Checked DEADLetter queue. NO messages related to the activity.(The message that are thre in DLQ are quite old, nothing that got logged today)
Transmission queue - No messages.
'SYSTEM.INTER.QMGR.PUBS' queue has many messages.
Kindly guide/suggest. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Tue Jan 15, 2013 11:54 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
I just tried via MQExplorer to publish messages for topicString 'MBC/03'.
I found similar behavior.
When published on QM3 explicitly, the subscriber on QM3 receives message. (message count/time in updated) and message is put onto destination.
When published on other QMs in the cluster, subscriber on QM3 DOES NOT receive message. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 15, 2013 11:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Do you have any of those cool cluster workload management attributes set that might account for this behavior?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Tue Jan 15, 2013 12:24 pm Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Nope.
We do not have anything specified. But just to be on safer side, can you tell me where to check.
I checked status on QM Pub/Sub - all are active and there is NO hierarchy defined as well.
Did refresh Proxy subscriptions as well - no luck. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 15, 2013 1:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Is the definition of the Topic object, or it's nearest defined parent, in QM3 identical as in the other qmgrs? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
