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 » What happen to Msgflow at Maximum client wait time

Post new topic  Reply to topic
 What happen to Msgflow at Maximum client wait time « View previous topic :: View next topic » 
Author Message
KIT_INC
PostPosted: Thu Mar 12, 2015 8:14 am    Post subject: What happen to Msgflow at Maximum client wait time Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

I am using WMB 7004 on Linux.
I am planning a msgflow as follow (using EG listener)

HTTPInput -- some nodes -- HTTPRequest (to vendor) ---- some nodes --HTTPReply


HTTPInput has Maximum client wait time of 5 sec
If I understand the Info center correctly, If the entire flow did not finish in 5 seconds (ie. no HTTPReply), HTTPInput will detect the timeout and if the timeout terminal is not connected, it will send a fault reply to the user.

My question is after this fault reply is sent , what will happen to the process that is still happening with the flow ? Here is what I think will happen, please help me to confirm if I am right or wrong.
1. The broker will consider the flow to be a failure and hence data base call or MQ calls (in some nodes)which has happened will be rolled back if transaction=yes is specified for the nodes.
2. If at the time, the HTTPRequest is still waiting for the response, it will be terminated without further waiting.

Is my thinking right ? and is there anything else I should consider ?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Mar 12, 2015 8:30 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Think it like that. If the response hits the reply node before the time out notification you're good. If not you will get an error on the good message saying something like token already used and go into error handling.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
KIT_INC
PostPosted: Thu Mar 12, 2015 11:16 am    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589

Hi fjb_saper., you said
Quote:
you will get an error on the good message saying something like token already used and go into error handling.


Do you mean that the message flow will continue to execute and finally get to the HTTPReply node and got the error because the HTTP.RequestIdentifer was already used by the 5 sec timeout fault sending back to the user ?
I was actually thinking that the flow will failed once the 5 second time out fault is sent.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Mar 12, 2015 12:45 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

KIT_INC wrote:
Hi fjb_saper., you said
Quote:
you will get an error on the good message saying something like token already used and go into error handling.


Do you mean that the message flow will continue to execute and finally get to the HTTPReply node and got the error because the HTTP.RequestIdentifer was already used by the 5 sec timeout fault sending back to the user ?
I was actually thinking that the flow will failed once the 5 second time out fault is sent.

Don't know at runtime, but that's the way it behaves in debug..
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ganesh
PostPosted: Fri Mar 13, 2015 8:33 am    Post subject: Reply with quote

Master

Joined: 18 Jul 2010
Posts: 294

KIT_INC wrote:
Hi fjb_saper., you said
Quote:
you will get an error on the good message saying something like token already used and go into error handling.


Do you mean that the message flow will continue to execute and finally get to the HTTPReply node and got the error because the HTTP.RequestIdentifer was already used by the 5 sec timeout fault sending back to the user ?
I was actually thinking that the flow will failed once the 5 second time out fault is sent.


Quote:
Do you mean that the message flow will continue to execute and finally get to the HTTPReply node and got the error because the HTTP.RequestIdentifer was already used by the 5 sec timeout fault sending back to the user ?


This was true for soap nodes in version 7 and there was a fix supplied in fix pack 6 (7.0.0.6), this may or may not apply for HTTP nodes.
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IC90615
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 » What happen to Msgflow at Maximum client wait time
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.