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 » Message being struck at Mq input node

Post new topic  Reply to topic
 Message being struck at Mq input node « View previous topic :: View next topic » 
Author Message
vikas.bhu
PostPosted: Wed Jul 18, 2012 10:20 pm    Post subject: Message being struck at Mq input node Reply with quote

Disciple

Joined: 17 May 2009
Posts: 159

Hi,

We have a simple flow as follows.
MQInput->Compute->Mqoutputnode->Compute->Mqget node->Compute-Mqoutput node.

if I am sending requset/response messages one by one flow is working fine.
But if I am not sendin the first response message. and Sending the second (Third,fourth..) request message ..all the mesage are piling up at first mqinput node itself.(I have set transaction mode as No every where).

Any help?
Back to top
View user's profile Send private message Send e-mail
vikas.bhu
PostPosted: Wed Jul 18, 2012 11:12 pm    Post subject: Reply with quote

Disciple

Joined: 17 May 2009
Posts: 159

Got the answer!!
It was very basic!!
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Wed Jul 18, 2012 11:15 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Would you care to share your solution just in case someone else sees the same behaviour?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
vikas.bhu
PostPosted: Thu Jul 19, 2012 8:10 pm    Post subject: Reply with quote

Disciple

Joined: 17 May 2009
Posts: 159

It was a synchoronous call through Get node.So,the thread will be active till the time specified in get node and messages will be piling up in the mq input node.

We should increase the number of instances to avoid this king of satuations up some extend.
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Fri Jul 20, 2012 5:21 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

vikas.bhu wrote:
We should increase the number of instances to avoid this king of satuations up some extend.


This is a band-aid solution. What's the real problem? Is the flow designed well?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
vikas.bhu
PostPosted: Fri Jul 20, 2012 9:14 pm    Post subject: Reply with quote

Disciple

Joined: 17 May 2009
Posts: 159

Actually there was very old WMB flow deployed in PROD which was interacting with legacy system.Recently there was some modification done in legacy system(some data or logic changed)and messages start piling up in WMB(due to time out).
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message being struck at Mq input node
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.