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 » WBI is sending rejected messages to the destination

Post new topic  Reply to topic
 WBI is sending rejected messages to the destination « View previous topic :: View next topic » 
Author Message
busy_chap
PostPosted: Mon Nov 05, 2007 12:53 pm    Post subject: WBI is sending rejected messages to the destination Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

Hello all,
I have a very strange situation and do not understand in which direction to troubleshoot.
Flow:
A CSV file is sent to WBI on AIX and if mappings successful , WBI sends it to destination. If not successful reject the whole message and send nothing to destination.

Issue:
WBI when rejects a input message for some reason is creating the output message and sends it to destination which is making our custmers very unhappy.

I have taken the same bar file that is causing this problem and deployed it to a different AIX box and when tested,it is working perfectly fine. It is only on one box that the flow is behaving wierdly.
Can anybody give me any direction. I have debugged it a 1000 times but found nothing wierd.I am pretty sure the flow is working fine , I have tested the flow in three environments and it is working fine.
Any ideas will be greatly appreciated.
Back to top
View user's profile Send private message
shalabh1976
PostPosted: Mon Nov 05, 2007 1:18 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

In the environment where the message are going to the wrong destination can you test if this behavior is happening for all flows.
For that matter if the mappings fail which queue is the message put to?
Try and throw an expicit failure and see what happens.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
busy_chap
PostPosted: Mon Nov 05, 2007 1:27 pm    Post subject: Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

Thanks for your quick response Shalabh. It is only this flow that has this problem. I really can't do any testing in that environment, as this is failing in Prod.When the message is rejected it is going to a Failure queue and for some reason , it is also going to the label where the output message is created.This is only happening in Prod. If I test in any other AIX box or local windows box , it is working perfectly fine with the message that is causing problem in Prod
Back to top
View user's profile Send private message
shalabh1976
PostPosted: Mon Nov 05, 2007 1:31 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

Is by any chance a destination list getting used. Also check if a DB is populating the destination list. Then check the DB values if that is the case.
Assuming you are facing a problem in production I am surprised the flow made it out of QA.
Is the prod environment not properly vetted?
Instead of using the production bar file what is the status of the file that was promoted to production from QA.
Also by any chance the bar file you see in prod is not the one that is deployed?
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
busy_chap
PostPosted: Mon Nov 05, 2007 1:36 pm    Post subject: Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

I will check the options that you have provided me with. To my utter surprise , it is the same bar file that is deployed in all the environments but I am seeing this issue only in Prod and we don't see this problem everyday. It has happened only twice but consistently that's what is making our customers very unhappy.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Nov 05, 2007 1:40 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Is there any chance you have a phantom EG on production?

Is there any chance that it's something specific with the exact message that's being sent through? Did you try the same message on the other, working, environments?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
shalabh1976
PostPosted: Mon Nov 05, 2007 1:41 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

If you have seen the problem only twice probably means that the flow is working fine at other times. Is it possible that in production you have received a file that has not been considered. Has this same input in a different environment produced a different output?
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
busy_chap
PostPosted: Mon Nov 05, 2007 1:46 pm    Post subject: Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

I have taken the exact same message that is causing this problem in Prod and tested in various environments and it is working perfectly fine as . An output message is not created and nothing is sent to the destination.If I had the same behavior in all the environments that would have amde my life easier but this unique behavior is really cutting down my options to debug.
Back to top
View user's profile Send private message
shalabh1976
PostPosted: Mon Nov 05, 2007 1:49 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

As Jeff suggested try looking for a phantom exec group (or rogue exec group). You can search by the number of DataFlowEngine (DFE) processes or look at the open input counts of the queues if you know exactly how many applications are feeding of them. Additionally if you search this forum/developerworks you will find quite a few mails dealing the phantom exec groups.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
busy_chap
PostPosted: Mon Nov 05, 2007 1:54 pm    Post subject: Reply with quote

Acolyte

Joined: 18 May 2006
Posts: 69

Thanks a lot Shalabh and Jeff. Atleast I have few options to look at.I will let you guys know if I find any fix.
Thanks again.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Nov 05, 2007 3:23 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Maybe its as simple as you have an old version of the flow deployed to another EG. When your current version of the flow gets lucky and gets the message it works fine. When the old version of the flow gets it you get the "unexpected" behaviour.

Do a queue status on the input queue. How many flows have it open?
_________________
Peter Potkay
Keep Calm and MQ On
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 » WBI is sending rejected messages to the destination
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.