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 IndexWebSphere Message Broker SupportWeird behaviour of Application after new deployed code

Post new topicReply to topic
Weird behaviour of Application after new deployed code View previous topic :: View next topic
Author Message
mqbrks
PostPosted: Sat Mar 16, 2019 7:54 pm Post subject: Weird behaviour of Application after new deployed code Reply with quote

Voyager

Joined: 17 Jan 2012
Posts: 75

Hi ,

We have a interface where we receive the file from source through Sterling and after transformation the Output file is transferred to the mailbox based on the vendor code within the filename.

Previously the same application use to route to a mailbox if the target type is File and to Output queues if target type is MQ.

With the new enhancement, two additional mailboxes are included based on the vendor code.

The same release bar file works good on TEST, but on Prod we see a weird behaviour, where even though the vendor code doesn't belong to a particular mailbox, it is routed to that mailbox. The same file when processed on test, is routed to correct mailbox. We have tried to delete the deployed resources and redeploy. When manually reprocessed from mqsiarchive, files are routed to appropriate mailboxes, but when files are received from sterling, few files are routed correctly and few incorrectly.

What could be the possible reason for this inconsistent behaviour ?

One thing to mention is we have migrated from one Version Management tool to another.

Any inputs please ? Should I delete the Integration Server and create a new IS, redeploy ?
Back to top
View user's profile Send private message
abhi_thri
PostPosted: Mon Mar 18, 2019 1:36 am Post subject: Reply with quote

Master

Joined: 17 Jul 2017
Posts: 263
Location: UK

hi...the best way to diagnose scenarios where the code behavior varies per environment is to collect traces (user/service) and analyze it, that will exactly tell you what the code is doing 'wrong'.

I guess there might be some environment specific differences coming into play, eg:- routing rule differences b/w Test & Prod, any routing caching logic rule (using the previously cached route) etc
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportWeird behaviour of Application after new deployed code
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.