| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Handling HTTP timeout |
« View previous topic :: View next topic » |
| Author |
Message
|
| ktg |
 Posted: Thu Jun 28, 2012 2:23 am Post subject: Handling HTTP timeout |
 |
|
Centurion
Joined: 09 Jan 2006
Posts: 138
Location: India
|
Hi All,
We have a HTTP request flow. Maximum client wait period is set to 2 seconds for the HTTP input node. If the processing is not getting completed in 2 seconds, the HTTP input node's timeout terminal is receiving timeout message. The timeout message will not be having any information about the original request message. So, we will not be knowing which request has been timed out. So, wont be able to send appropriate error response to the initial requester. How to handle this case? Please, advise.
TIA.
Regards,
Kalpana |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jun 28, 2012 3:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The timeout terminal gets fired in a new instance of the message flow, because one of the reasons the terminal might get fired is because the main instance of the message flow has died completely or otherwise is unresponsive or stuck.
You can use a SHARED variable to hold state about the main instance of the message flow. This will then be available in the timeout - but you have to code it so you can correlate the right state with the timeout terminal that's fired. That is, so you don't send a timeout response with the wrong information.
This won't necessarily let you know the real cause for the timeout, however. but it should get you closer.
Make a list of the pieces of information you really need available in case of a timeout. It might not be as much as you think it is. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Jun 28, 2012 3:40 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1639
|
Actually, if you put a trace node into your flow after the TimeOut terminal and trace $LocalEnvironment you will see some information about the timed out message as well as a BLOB version of the timed out message...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
