| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to identify the subscribers for topics on MQ 7.5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mangesh1187 |
 Posted: Wed Jun 25, 2014 11:26 pm Post subject: How to identify the subscribers for topics on MQ 7.5 |
 |
|
Centurion
Joined: 23 Mar 2013
Posts: 116
|
Hi All,
I am using the MQ 7.5. I am remtely connceted to the Queue Manager QM1 using MQ explerer & publishing the mssages using the MQ Explorer tool to the topic : TEST/TOPIC1/TOPIC2
I have created one Administrative SUB to subscribe it. And also 2 JMS applications using WAS durably subscribing the similer topic. So there should be 3 subscribers.
Now I want to identify the which are these subscriber applications.
I gone through the link http://www-01.ibm.com/support/docview.wss?uid=swg21375536 & followed below command.
display tpstatus(TEST/TOPIC1/TOPIC2) type(sub)
37 : display tpstatus(TEST/TOPIC1/TOPIC2) type(sub)
AMQ8754: Display topic status details.
TOPICSTR(TEST/TOPIC1/TOPIC2)
SUBID(414D5120514D31202020202020202020381CA053200EAB13)
SUBUSER(mangesh) RESMDATE( )
RESMTIME( ) LMSGDATE(2014-06-26)
LMSGTIME(12:19:14)
ACTCONN(000000000000000000000000000000000000000000000000)
DURABLE(YES) SUBTYPE(ADMIN)
MCASTREL( , ) NUMMSGS(152)
AMQ8754: Display topic status details.
TOPICSTR(TEST/TOPIC1/TOPIC2)
SUBID(414D5120514D31202020202020202020381CA053201F239C)
SUBUSER(mangesh) RESMDATE(2014-06-24)
RESMTIME(17:24:54) LMSGDATE(2014-06-26)
LMSGTIME(12:19:14)
ACTCONN(000000000000000000000000000000000000000000000000)
DURABLE(YES) SUBTYPE(API)
MCASTREL( , ) NUMMSGS(152)
AMQ8754: Display topic status details.
TOPICSTR(TEST/TOPIC1/TOPIC2)
SUBID(414D5120514D31202020202020202020381CA05320267501)
SUBUSER(mangesh) RESMDATE(2014-06-25)
RESMTIME(23:51:13) LMSGDATE(2014-06-26)
LMSGTIME(12:19:14)
ACTCONN(000000000000000000000000000000000000000000000000)
DURABLE(YES) SUBTYPE(API)
MCASTREL( , ) NUMMSGS(152)
The above o/p shows 3 subscribers but all having similer ACTCONN prepoerty. I expected 3 diffferent ACTCONNs.
And when I checked for the CONN (last 16 digits of ACTCONN) it shows below :
display conn(0000000000000000)
38 : display conn(0000000000000000)
AMQ8276: Display Connection details.
CONN(9D03A95320001101)
EXTCONN(414D5143514D31202020202020202020)
TYPE(CONN)
PID(4708) TID(2)
APPLDESC(WebSphere MQ Queued Pub/Sub Controller)
APPLTAG(ebSphere MQ\bin\amqfqpub.exe) APPLTYPE(SYSTEM)
ASTATE(NONE) CHANNEL( )
CONNAME( ) CONNOPTS(MQCNO_FASTPATH_BINDING)
USERID(mangesh) UOWLOG( )
UOWSTDA( ) UOWSTTI( )
UOWLOGDA( ) UOWLOGTI( )
URTYPE(QMGR)
EXTURID(XA_FORMATID[] XA_GTRID[] XA_BQUAL[])
QMURID(0.0) UOWSTATE(NONE)
It seems the information for my Administrative subscibers. How can I identify the other 2 JMS appilcaitons who are susbcribing the mentioned topic ?
Also in above o/p CONN(9D03A95320001101) shows different ID than what I mentioned in display conn(0000000000000000) command.
Note these applicaions are unsing below SVRCONN channel to connect to QM1.
display chl(channel3)
40 : display chl(channel3)
AMQ8414: Display Channel details.
CHANNEL(CHANNEL3) CHLTYPE(SVRCONN)
ALTDATE(2014-06-19) ALTTIME(11.49.15)
COMPHDR(NONE) COMPMSG(NONE)
DESCR( ) DISCINT(0)
HBINT(300) KAINT(AUTO)
MAXINST(999999999) MAXINSTC(999999999)
MAXMSGL(4194304) MCAUSER(mangesh)
MONCHL(QMGR) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SHARECNV(10)
SSLCAUTH(REQUIRED) SSLCIPH( )
SSLPEER( ) TRPTYPE(TCP)
Kindly guide me. |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu Jun 26, 2014 12:02 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I always use MO71 to examine subscriptions.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| dware |
| Posted: Wed Jul 02, 2014 7:41 am Post subject: |
|
|
Novice
Joined: 18 Nov 2013
Posts: 13
|
Hi,
The ACTCONN value is the MQ connection id of the application that currently has the subscription open. If you're getting back all zeros in ACTCONN it means no application has it open at this point in time. As you're dealing with durable subscriptions, that sounds perfectly reasonable. If the JMS applications were running at the time you did the display, you should see actual values which you could then use DISPLAY CONN to investigate further.
Another thing you can look at on the subscriptions to differentiate them is their subscriptions names. They're not returned as part of DISPLAY TPSTATUS so you'll need to see them using DISPLAY SUB, this returns the subscription configuration rather than it's current status.
Regarding you getting back a valid connection when you pass in all zeros looks like a bit of a bug to me, you might like to get that investigated by MQ service.
David |
|
| 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
|
|
|
|
