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 » IBM MQ Performance Monitoring » Tivoli handling MQ channel out of sequence

Post new topic  Reply to topic Goto page Previous  1, 2
 Tivoli handling MQ channel out of sequence « View previous topic :: View next topic » 
Author Message
Vitor
PostPosted: Wed Apr 02, 2008 12:25 am    Post subject: Reply with quote

Grand High Poobah

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

angka wrote:
But comparing the ID is what IBM suggested in their Redbook when encountering out of sequence issue. Does that mean by comparing the ID may not correctly show whether the previous batch of messages is received by the receiver?


It's a suggested method as you say. It's only a suggestion, and is not definative. Like I said, if it was as easy as comparing ID numbers, the MCAs would do it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
angka
PostPosted: Wed Apr 02, 2008 3:11 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

Thanks.

Looks like no other way to handle this. I will try to ask the receiver to raise PMR.
Back to top
View user's profile Send private message
angka
PostPosted: Wed Apr 02, 2008 3:15 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

Are there any redbook on what Tivoli Omegamon XE for Messaging can detect e.g channel out of sequence then it will handle it accordingly to user defined? I had the MQ configuration user guide and the MQ monitoring user guide but nothing is mention on what can be detected etc.

Thanks.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Apr 02, 2008 3:21 am    Post subject: Reply with quote

Grand High Poobah

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

angka wrote:
Looks like no other way to handle this.


Aside from fixing the root cause of the channel sequence errors. Which (at the risk of sounding like a broken record) shouldn't happen so often you need to automate the reset.

angka wrote:
I will try to ask the receiver to raise PMR


You're going to ask IBM to provide a patch so that channels don't go in doubt on sequence errors???
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Wed Apr 02, 2008 7:39 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

I assume he assumes his sequence #s are being maintained correctly and the PMR will be to see why the receiver's seq #s are changing unexpectedly. They could be changing unexpectedly because of a bug, or accidental or malicious changing by a human.

Maybe they got some dumb script that says reset all the channel seq #s upon a QM restart for a "fresh start". Dumb for normal business. Not odd at al in a DR failover scenario.

angka, your questions on why the seq #s don't resolve automatically are not that wild. The manuals do give a very step by step process to determine if you should commit or back out. I've often wondered why that can't happen automatically if its so 1,2,3,4,5 as to how to make that call. I wonder less now because my channels are properly configured and seq # errors are extremely rare. Maybe its manual for the sole reason that if it happened automatically it would mask the frequent seq # errors which are a sign of a bigger problem.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
angka
PostPosted: Thu Apr 03, 2008 12:00 am    Post subject: Reply with quote

Chevalier

Joined: 20 Sep 2005
Posts: 406

Hi,

Ya PeterPotkay is right, I mean raise PMR to see why out of sequence keeps happening. I did look at their MQ log and their event log, their Queue Manager keep restarting on it own and i believe their system is set up full of problems. However, I have no rights to interfere therefore, to prevent my system to be affected due to their problem i hope to resolve the out of sequence issue automatically.

Btw can Tivoli Omegamon for Messaging track that the sender and receiver is in doubt with out of sequence as the problem so that we can configure to resolve with backout automatically?

I have not use Tivoli before and know that there is alot of stuff that this tool can monitor but is there a redbook on the specific thing it can do for messaging?

Thank you
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » IBM MQ Performance Monitoring » Tivoli handling MQ channel out of sequence
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.