|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Handling Runtime, Timeout, Connection Exception in ESQL |
« View previous topic :: View next topic » |
Author |
Message
|
sathish.mani |
Posted: Fri Dec 19, 2014 7:30 am Post subject: Handling Runtime, Timeout, Connection Exception in ESQL |
|
|
Newbie
Joined: 19 Nov 2014 Posts: 8
|
I am new to Message broker and need a little help in handling exceptions in ESQL compute node.
I have an ESQL node at the failure terminal that creates a structure with three tags.
1. Faultcode, which is the error code given by MB for any particular exception
2. FaultString, which is the variable that is causing the error
3. Detail, which contains all the exception messages in the exception tree structure.
Now my requirement is based on the exception that is generated, i need to assign a custom code(in place of fault code) and custom message(in place of fault string).
This is how my ESQL looks like
IF CONTAINS(detail,'Error Making JNI Call') THEN
SET OutputRoot.SOAP.Body.soapenv:Fault.faultcode = '7200';
SET OutputRoot.SOAP.Body.soapenv:Fault.faultstring = ' Connection Exception while connecting to target system';
END If;
But I dont know what string exactly the exception list has to use it IF CONTAINS statement for other type of exceptions like time out, input validation, run time exceptions.
I would appreciate any help  |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Dec 19, 2014 7:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There's a complete list of all of the hundreds of possible error messages that Broker/IIB can produce in the Knowledge Center. |
|
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
|
|
|
|