| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Request/reply with timout over MQ design issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| alefrasca |
 Posted: Thu Jun 14, 2007 12:40 am Post subject: Request/reply with timout over MQ design issue |
 |
|
Newbie
Joined: 28 Feb 2006
Posts: 4
|
I need to write a Message flow that interacts with a java application developed on WAS using WebSphere MQ queues.
The broker sends a message request and receives a response message or a fault message and needs to manage the timeout of the response.
The number of the message that will be processed is very high so I need to create a design to enhance the performances.
My doubts are
1) I’m not sure about which is the best approach to manage timeout in a high volume messages environment ( aggregate request nodes, mqget, SOAP/JMS)
2) I need to create a general design of a message that can handle different kind of request/response/fault message. Can I use a SOAP-LIKE message even if the best approach won’t be SOAP/JMS protocol
3) Does anybody know a good article/redbook about this?[/b] |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Thu Jun 14, 2007 4:25 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi alefrasca,
For better performace, it would have been a great idea to keep the request and response flows disjoint...such that you could keep firing requests while not waiting for the responses, and correlate the response for the original calling system by storing their msgId into the WAS request msg...
But then you want to work with timeout....what do u plan to do if the WAS app. replies after a timeout ? How will you know whether you have already replied or not replied for that response ? In that case, HTTP seems to be the only option out...or atleast a good option 
Regards. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 14, 2007 2:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you keep the response in the same flow you can use a Get Node (V6). You may need multiple instances of the flow to handle the volume. The timeout can be set to the milisecond.
If your timeout value is by seconds you can use an aggregate node approach... with 2 flows....
An aggregation fan out request flow that sets the timeout and an aggregation fan it flow that handles the reply part of the processing....
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| alefrasca |
| Posted: Wed Jun 27, 2007 2:29 am Post subject: final solution |
|
|
Newbie
Joined: 28 Feb 2006
Posts: 4
|
Thank you very much for the help. For now I will use the aggregate nodes passing the original messag too from the fan out and the fan flow.
I saw other POCs using a similar solution so I'm quite confident that it works. The timeout and message that arrives after timeout are managed by the aggregation flow .
Im writing the code right now to menage all the situations |
|
| 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
|
|
|
|
