| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unexpected termination before timeout control node |
« View previous topic :: View next topic » |
| Author |
Message
|
| jkr |
 Posted: Tue May 10, 2016 6:46 am Post subject: Unexpected termination before timeout control node |
 |
|
Novice
Joined: 19 Apr 2016
Posts: 10
|
I have a message flows which goes like this
Http Input-->Compute-->http request(error)-->compute-->Timeout control
I am setting the control message for the timeout control node in the compute node that i've put before it.
When I just pass the control message in compute node the flow works perfectly fine,but when I put something else along with it, like the entire
InputRoot, the flow terminates right before the timeout control node.
| Code: |
SET OutputLocalEnvironment.Data.TimeoutRequest.Action = 'SET';
SET OutputLocalEnvironment.Data.TimeoutRequest.Identifier = 'AsyncId3';
SET OutputLocalEnvironment.Data.TimeoutRequest.StartDate = 'TODAY';
SET OutputLocalEnvironment.Data.TimeoutRequest.StartTime = 'NOW';
SET OutputLocalEnvironment.Data.TimeoutRequest.Interval=2;
SET OutputLocalEnvironment.Data.TimeoutRequest.Count = 5;
SET OutputLocalEnvironment.Data.TimeoutRequest.IgnoreMissed = FALSE;
SET OutputLocalEnvironment.Data.TimeoutRequest.AllowOverwrite = FALSE; |
The above code works perfectly fine but when I add the below line to it or any other code for that matter,it terminates unexpectantly
| Code: |
| Set OutputRoot.XMLNSC=InputRoot.XMLNSC; |
I have set the request location in Timeout control node,is there anything else that is supposed to be done?
[/code] |
|
| Back to top |
|
 |
| timber |
| Posted: Tue May 10, 2016 6:59 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| it terminates unexpectantly |
If possible, use the command-line tools in the IIB console to take a user trace.
The tools are mqsichangetrace, mqsireadlog, mqsiformatlog.
The instructions for taking a user trace are in the Knowledge Center and probably somewhere on this forum. |
|
| Back to top |
|
|
| jkr |
| Posted: Wed May 11, 2016 12:14 am Post subject: |
|
|
Novice
Joined: 19 Apr 2016
Posts: 10
|
I am reading on User Trace but meanwhile,when i check the system log,I encounter the following error:
An error occurred in parser ''Root'' while parsing the field named ''MQMD'' on behalf of the node or component 'xxx.xxxx.asyncservice.AsynchronousService.Timeout Notification'. The data being parsed was ''Null Buffer''. |
|
| Back to top |
|
|
| maurito |
| Posted: Wed May 11, 2016 1:02 am Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| jkr wrote: |
I am reading on User Trace but meanwhile,when i check the system log,I encounter the following error:
An error occurred in parser ''Root'' while parsing the field named ''MQMD'' on behalf of the node or component 'xxx.xxxx.asyncservice.AsynchronousService.Timeout Notification'. The data being parsed was ''Null Buffer''. |
I seem to remember this is a 'feature'. Add a MQHeader node after the compute node and configure it to add a header. |
|
| Back to top |
|
|
| jkr |
| Posted: Wed May 11, 2016 1:12 am Post subject: |
|
|
Novice
Joined: 19 Apr 2016
Posts: 10
|
Thanks for the reply maurito, I did just that.
Turns out I hadn't added an MQMD header before the Timeout Control node.
Adding the below two lined solved the problem
CREATE NEXTSIBLING OF OutputRoot.Properties DOMAIN 'MQMD';
SET OutputRoot.MQMD.Version = MQMD_CURRENT_VERSION;
Also,thanks to timber for giving me the sense to check the logs. |
|
| 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
|
|
|
|
