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 » Wierd mqsichangetrace issue

Post new topic  Reply to topic
 Wierd mqsichangetrace issue « View previous topic :: View next topic » 
Author Message
busy_chap
PostPosted: Wed Jun 25, 2008 1:03 pm    Post subject: Wierd mqsichangetrace issue Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

Hello everybody,
We have a very weird issue. I am hoping somebody will give me some info.

In our Prod environment on AIX,the Input messages have to go through two WBI flows.
1. First flow validates a field in the input message which is in XML format as '123' and routes the message to the second flow.If the field value is not '123' , the message will error out.

2. Second flow also checks for the field '123' and routes the message to a output q.If the field value is not '123' , the message will error out.

The issue is that the first message flow processed the message and sent it to the second flow.
The second flow checks for '123' and for some reason thinks that value is not '123' and errors out the message.
Just 5 min ago we were having this issue. We thought we will run mqsichangetrace and see why the second flow does not detect that field as '123'.
To our utter surprise from the moment we ran the mqsichnagetrace, it is working fine.

Did anybody face this wierd issue? Does mqsichnagetrace help process a message? We are so surprised because 5min ago the message was getting processed in the second flow and from the moment we ran the mqsichangetrace it's working fine.

Please respond.
Back to top
View user's profile Send private message
broker_new
PostPosted: Wed Jun 25, 2008 2:35 pm    Post subject: Reply with quote

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC

How you are checking the value of the field can you post the ESQL.
Back to top
View user's profile Send private message
sri_csee1983
PostPosted: Wed Jun 25, 2008 5:19 pm    Post subject: Reply with quote

Centurion

Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India

R u sure, your first flow was working fine? I mean with the input to the first flow was 123 and also did u check whether the input to the second flow went in correctly (I mean 123). Can u also post the trace of both the flows? Bcoz this really a wierd one.
_________________
With Cheers,
Sri
Back to top
View user's profile Send private message Send e-mail Visit poster's website
vsr
PostPosted: Thu Jun 26, 2008 5:04 am    Post subject: Re: Wierd mqsichangetrace issue Reply with quote

Centurion

Joined: 04 Apr 2006
Posts: 104

busy_chap wrote:
To our utter surprise from the moment we ran the mqsichnagetrace, it is working fine.

It's common thing that sometimes we explore different options and overlook simple things. I guess it's not mqsichangetrace that made your flows working, may be the logic in the 2nd flow made the flow error out. May be the error that is generated is not the error you thought it would be !?. Check your error handling and business logic in the flow.
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 » Wierd mqsichangetrace 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.