ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange Issue

Post new topic  Reply to topic
 Strange Issue « View previous topic :: View next topic » 
Author Message
gag_nm
PostPosted: Fri Sep 30, 2011 5:17 am    Post subject: Strange Issue Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

Dear Friends,

I don't know where to Post this topic either MQ or IBM Message Broker.

we have MQ cluster environment and Message Broker Queue Manager is also part of it. Broker Queue Manager is Full Repository(FR) and Remaing are Partial Repository(PR) .

Issue is among all Request messages coming from PR Queuemanager , only some them are reaching Broker,i am facing strange issue if two messages are reaching Broker then next immediate 1 or 2 messages are not reaching Broker. this is happening from each of the Partial Repository Queue Manager

i have restarted FR queue manager and PR queue managers, but no use.
i even did reset and resolve at each end of the queue manager channels.

please give me some suggestions, where all i have to check to find out probelm.let me know areas where i might have missed out to check...( inluding broker area)


Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Sep 30, 2011 5:28 am    Post subject: Re: Strange Issue Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

gag_nm wrote:
i have restarted FR queue manager and PR queue managers, but no use.
i even did reset and resolve at each end of the queue manager channels.


Based on anything apart from hope? Error messages, odd statuses, etc?

gag_nm wrote:
please give me some suggestions, where all i have to check to find out probelm.


All the usual places for a WMQ cluster problem. If the messages are not reaching broker then your cluster is broken, possibly because you've been issuing random reset & resolve commands. Seriously. A RESET CLUSTER, used importly can be dangerous.

Stop the flow and send some messages. This will prove if the messages are not arriving or WMB is discarding them. If (as I suspect) it's the former check your cluster.

If it's the latter, run user trace on the flow.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Fri Sep 30, 2011 5:34 am    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland

Hi,

Simple questions, but:

Are the queues in broker qmgr unique or are there queues with same name in the other qmgrs too?

Have you found the "lost" messages some where (from system queues for example)?

What version of MQ are you using?

--
Marko
Back to top
View user's profile Send private message Visit poster's website
gag_nm
PostPosted: Fri Sep 30, 2011 6:13 am    Post subject: Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

Marko

i did not find missing messages in any queue.

i stopped broker flows as well. but as i said only few messages which reach broker queue manager are laying in queues .

do need to RESET CLUSTER or remove cluster and try with new cluster.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Sep 30, 2011 6:48 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

gag_nm wrote:
i stopped broker flows as well. but as i said only few messages which reach broker queue manager are laying in queues .


So the cluster is not delivering all the messages.

gag_nm wrote:
do need to RESET CLUSTER or remove cluster and try with new cluster.


You need to think about you next move, not randomly grab at a likely sounding command, or try rebuilding the cluster in the hope you don't reproduce whatever's wrong with this one the next time.

Diagnose the problem, then fix it. Something is wrong with your cluster. Use the tools to find what it is. Make sure everything is as you expect it to be and that it's all running as expected. No retrying channels, no temporary queue manager names in the cluster displays, that sort of thing.

Only if that fails consider a new cluster, and before building consider what might have gone wrong this time. Plan the cluster up front, script the objects and verify each step.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Sep 30, 2011 8:32 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Whether or not a qmgr is an FR or a PR has nothing to do with how messages are delivered to it over the cluster.

So IGNORE THAT.

Focus entirely and only on the queue in question.

HOW MANY instances of the queue are SHARED in the cluster?

Do you see, for example, that DIS QCLUSTER shows MORE THAN ONE of the same name?
Back to top
View user's profile Send private message
gag_nm
PostPosted: Fri Sep 30, 2011 10:57 pm    Post subject: Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

I started checking with each and every thing in MQ Cluster.

every thing was looking fine from Cluster point of view.but one queue at Broker Queue Manager input Count was 6, actullay it was supposed to be 1 or 2.

then I verified what all applications opening that queue with
DISPALY QUEUE(queue name) TYPE (HANDLE) command.then i could see one PID was opening queue and it was consuming messages.

PID was one of the Broker Execution group.then i stopped respective execution group, then i was getting response for each and every request.

one of the flow in that execuution group was consuming messages and discarding them.

Thanks to each and every one for support.
Back to top
View user's profile Send private message
MrSmith
PostPosted: Wed Oct 05, 2011 6:19 am    Post subject: Reply with quote

Master

Joined: 20 Mar 2008
Posts: 215

Quote:
Broker Queue Manager is Full Repository(FR) and Remaing are Partial Repository(PR) .


Not that it will help find your messages or resolve the issue that you report here (think suggestions have been propsed to address this but as a design thought, having your Broker QM as the FR for your Cluster or one thereof (you dont say how many FR you have) to me would not be the smartest move either, if your Broker were to go "bust" and take your QM with it you will also potentially lose one or your only FR - sure have it on the same box but not as the QM running your Broker - bit like storing matches in your TNT box....
Back to top
View user's profile Send private message
gag_nm
PostPosted: Sat Oct 08, 2011 1:13 am    Post subject: Reply with quote

Centurion

Joined: 16 Oct 2008
Posts: 102

Mr Smith,

The problem which i have faced was in development environment.

we have 2 FR queue managers in Development as well, one of them is Broker Queue Manager and Other is Some Application Queue Manager.


some queues are shared in cluster at broker queue manager, that is the reason, i mentioned
Broker Queue Manager is Full Repository(FR) and Remaing are Partial Repository(PR) .
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange Issue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.