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 » WMQI publish/subscribe problems

Post new topic  Reply to topic
 WMQI publish/subscribe problems « View previous topic :: View next topic » 
Author Message
JohnMetcalfe
PostPosted: Wed Nov 09, 2005 10:06 am    Post subject: WMQI publish/subscribe problems Reply with quote

Apprentice

Joined: 02 Apr 2004
Posts: 40
Location: Edinburgh, Scotland

Hi there,

We are hitting a sporadic problem with WMQI pub/sub (we are on WMQI 2.1 CSD3)

Occasionally, the publication seems to stop working i.e no messages arrive on the subscription Q(s), even though the publication flow does not throw any exceptions, the subscriptions are all present and correct in the broker and the broker pub/sub engine also reports no errors - we are requesting report messages from the pub\sub engine via the Report & ReplyToQ fields as follows:
SET OutputRoot.MQMD.Report = MQRO_NAN;
SET OutputRoot.MQMD.ReplyToQ = 'SLI.EXCEPTION_PUBSUB';

Restarting the execution group that contains the publication flow seems to 'fix' the problem. Everything seems to work OK again !!!

We have a number of issues:
1. While this has never happened in production, it has happened numerous times in our final user acceptance test environment, so our confidence level that this will never happen in prod is very low.
2. We can't reproduce the problem at will, so the response we raised to the PMR with IBM was a brush off.
3. Everyone seems to think that implementing a full blown monitoring tool is the soln, but this comes with a load of cost and effort, and all we want to be able to do is to monitor for pub\sub failures.

My question is has anybody else using pub\sub encountered similar problems, and if so what where their thoughts on a solution?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 09, 2005 10:09 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

My suspicion would be that something is causing the publication flow to hang - possibly a poison message..

I would say that you could get some useful information out of the performance stats... but you're using 2.1 which doesn't publish performance stats...

I would certainly start by applying a more recent CSD than 3.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JohnMetcalfe
PostPosted: Wed Nov 09, 2005 10:42 am    Post subject: Reply with quote

Apprentice

Joined: 02 Apr 2004
Posts: 40
Location: Edinburgh, Scotland

Jeff, thanks for this.

We are seeing the message being read off the input Q, and no message turning up in the DL Q, or the specified poinson message Q - all looks like the flow has completd OK. I've asked the support guys to trace the pub flow next time it happens so we can see if the WMQI trace can provide any clues as to what is happening. The problem is normally that it happens at some inconvenient time when we need to have the environment up, so the support guys just restart the execution group rather than try and find out what is going on.

We are planning the move up to WBIMB 5 (in fact we may try and go straight to 6), but I though it might be worth a try to see if anyone else out there in the community had encountered the problems - pub\sub is key to our whole architecture, and its absolutekly key that we have total confidence in it, and can detect when anything does not work as it is intended!
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Nov 09, 2005 10:47 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's probably better to go straight to 6.

The migration is supposed to be easier, for one. For two, the environments can fully coexist, so you don't have to provision new hardware, or remove old environments to make way for new ones.
_________________
I am *not* the model of the modern major general.
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 » WMQI publish/subscribe problems
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.