| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Design Query |
« View previous topic :: View next topic » |
| Author |
Message
|
| manoj5007 |
 Posted: Thu May 05, 2016 3:58 am Post subject: Design Query |
 |
|
Acolyte
Joined: 15 May 2013
Posts: 64
|
Hi
The requirement is, I get a number of line details in a single MQ mesasge and each line detail needs to be sent to a destination system over SOAP as individual request.
My question is , when the first line detail fails due to connectivity issue, wherein the control is sent to the failure terminal of SOAP Request Node, I need to terminate the message processing completely. And move the original message to a error queue to be replayed later
i can achieve this using a throw node or throw statement post the failure from SOAP Request Node.
But would like to know whether there is a better way of acheiving it.
Thanks
Manoj |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu May 05, 2016 5:29 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Your site may well have a standard way of handling errors. you really should look into that before re-inventing the wheel.
This is normally connected to the CATCH terminal of the flow input node.
Then a throw will rethrow the errors If your input queue has a BOQ defined then the original message will be sent to that queue. If that BOQ happens to be the error queue you talk about then you don't have to do anything else.
Well, that is the case in many sites who have invested the time and effort to setup all sorts of nice logging, auditing and error frameworks for you.
If yours has not, then you might like to ask why this has not been done?
There is a lof to gain from having this framework/infrastructure especailly developer productivity.
_________________
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 |
|
|
| manoj5007 |
| Posted: Thu May 05, 2016 6:29 pm Post subject: |
|
|
Acolyte
Joined: 15 May 2013
Posts: 64
|
The message being moved the error queue is fine.
The bigger question is suppose i have 5 line items, on encountering connectivity issue while the request of 1st line item is processed, I don't want the other 4 line items to processed and the message processing to be terminated.
In this case is Throw the only way ?? |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu May 05, 2016 9:36 pm Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| manoj5007 wrote: |
The message being moved the error queue is fine.
The bigger question is suppose i have 5 line items, on encountering connectivity issue while the request of 1st line item is processed, I don't want the other 4 line items to processed and the message processing to be terminated.
In this case is Throw the only way ?? |
Dont connect your SOAP Request Node's failure terminal. Then you dont have to use a Throw explicitly. Then the Broker takes care of pushing it to the Input Nodes catch terminal where your Error handling framework does the rest. |
|
| 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
|
|
|
|
