| Author |
Message
|
| jovual143 |
 Posted: Sat Mar 02, 2013 1:15 pm Post subject: Subscription is not picking messages |
 |
|
Newbie
Joined: 01 Mar 2013
Posts: 3
|
Hi all,
we have a scenerio where, the pub q will publish the messages. based on the topic the subscriptions will take the messages. unfortunately the same is working on one server and not on the other server. both are configured exactly and we are not seeing anything in the logs as well.
Though messages are not picking by sub, still the PUT time is getting updated.
can some one put light on this issue. any suggestions deeply appreciated.
FYI ...
QUEUE(XYZ.PUB) TYPE(QUEUE)
CURDEPTH(0) IPPROCS(1)
LGETDATE(2013-03-01) LGETTIME(02.35.09)
LPUTDATE(2013-03-01) LPUTTIME(02.35.09)
QUEUE(XYZ.SUB) TYPE(QUEUE)
CURDEPTH(0) IPPROCS(1)
LGETDATE( ) LGETTIME( )
LPUTDATE(2013-03-01) LPUTTIME(02.35.10) |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat Mar 02, 2013 1:36 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
queues don't publish messages.
applications do.
Topics don't publish messages.
applications do.
If you can't tell if messages are being produced, stop all applications that read messages. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Mar 02, 2013 1:44 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Are you just guessing at how to implement pub/sub? Or are you working from a document of some kind?
_________________
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 |
|
|
| jovual143 |
| Posted: Sat Mar 02, 2013 1:55 pm Post subject: |
|
|
Newbie
Joined: 01 Mar 2013
Posts: 3
|
sorry if i put the question in a wrong way.
this how the flow goes :
XYZ app -> XYZ pub Q/msg flow -> Topic abc -> abc sub -> abc sub q/msg flow
i am just trying to explain that the sub q is not picking the messages based on the topic, where as the same is working fine in the other server. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Mar 02, 2013 2:01 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Are you telling us that you have Message Broker?
_________________
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 |
|
|
| Vitor |
| Posted: Sun Mar 03, 2013 5:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jovual143 wrote: |
| i am just trying to explain that the sub q is not picking the messages based on the topic, where as the same is working fine in the other server. |
If what you're saying is that the subscribing application picks up the message if the target queue is on the same server as the publisher, but does not if it's on a different server, then the first place to look is clearly what communication you have between the two servers and whatever mechanisms you've implemented to ensure subscribed messages will flow between them.
I also echo the comment of my worthy associate; it's ambiguous if you mean "flow" is the sense of the Message Broker artifact or "flow" is the sense of "the movement of data through my estate.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Mon Mar 04, 2013 9:02 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Well, I would create a dummy subscriber for the TOPIC in question.
U can use explorer for the same.
Check the subscription status as well as destination queue once you publish the message.
If message is being put on the destination queue of dummy subscriber or subscription count is getting increased, then you know PUBLICATION is okay..there might be some problem with your subscribers.
You may want to check/compare the authentication being provided on both queue managers and also make sure the UserId which is publishing message is part of the group authorized to publish. |
|
| Back to top |
|
|
|
|
