|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
TimeOut Control/Notification generating GENERICPROPERTYPARSE |
« View previous topic :: View next topic » |
Author |
Message
|
williad |
Posted: Tue Mar 17, 2009 4:49 am Post subject: TimeOut Control/Notification generating GENERICPROPERTYPARSE |
|
|
Apprentice
Joined: 08 Sep 2005 Posts: 40 Location: London
|
Hi
I hope this make sense:
I have a compute node that is creating a message. Which is connected to a trace node,
and this trace node is connected to a subflow called "Delayed" which contains the TimeOut Control/Notification nodes. The TimeOut Cnntrol/Notification is set to 8 seconds before sending the message onwards. The way i have done this is shown below in a compute node with propagated values for the unique id, and time interval:
SET OutputRoot = InputRoot;
-- Use the interval to determine at what time this message should trigger
DECLARE DELAYINTERVAL INTERVAL;
SET DELAYINTERVAL = CAST(delayInterval AS INTERVAL SECOND);
DECLARE OUTPUTTIMESTAMP TIMESTAMP CURRENT_TIMESTAMP + DELAYINTERVAL;
-- Setup timer
SET OutputLocalEnvironment.TimeoutRequest.Action = 'SET';
SET OutputLocalEnvironment.TimeoutRequest.Identifier = UUIDASCHAR;
SET OutputLocalEnvironment.TimeoutRequest.StartDate = CAST(OUTPUTTIMESTAMP AS DATE);
SET OutputLocalEnvironment.TimeoutRequest.StartTime = CAST(OUTPUTTIMESTAMP AS TIME);
SET OutputLocalEnvironment.TimeoutRequest.Count = 1;
SET OutputLocalEnvironment.TimeoutRequest.IgnoreMissed = FALSE;
SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = FALSE;
The output of the "Delayed" subflow is connected to a trace node(1), and the then onto a MQ Output node.
When i look at the first trace message after the compute node i see the following:
44 UserTrace BIP4060I: Data ''( ['MQROOT' : 0x114d51f00]
(0x01000000:Name ):Properties = ( ['MQPROPERTYPARSER' : 0x114cc6268]
(0x03000000:NameValue):MessageSet = 'DL02IJ407Q001' (CHARACTER)
(0x03000000:NameValue):MessageType = 'm_FileFromAdapter' (CHARACTER)
(0x03000000:NameValue):MessageFormat = 'CWF' (CHARACTER)
The trace after the "Delayed" subflow shows
UserTrace BIP4060I: Data ''( ['GENERICROOT' : 0x101e20e10]
(0x01000000:Name ):Properties = ( ['GENERICPROPERTYPARSER' : 0x101e81a28]
(0x03000000:NameValue):MessageSet = 'DL02IJ407Q001' (CHARACTER)
(0x03000000:NameValue):MessageType = 'm_FileFromAdapter' (CHARACTER)
(0x03000000:NameValue):MessageFormat = 'CWF' (CHARACTER)
When the message then goes to a mq output node, it fails. If i take out the timeout subflow, and the compute node connects to the MQ Output node directly, it works fine.
I think the problem is becuase of this GENERICROOT/GENERICPROPERTYPARSER property setting. I dont know why this isnt the same as when the message first went into the Delayed Subflow.
Can someone please point me in the rigfht direction in how to get the message that goes into the Timeout subflow have the same setting when it comes out?
Thanks |
|
Back to top |
|
 |
williad |
Posted: Fri Mar 27, 2009 3:35 am Post subject: |
|
|
Apprentice
Joined: 08 Sep 2005 Posts: 40 Location: London
|
I called IBM about this, and they said that it seems like its a bug with the timeout/notification control, and they have passed it onto their labs |
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 27, 2009 3:36 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Moving off topic slightly, why an 8 second delay in processing? What's the requirement? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
williad |
Posted: Mon Apr 13, 2009 9:04 am Post subject: |
|
|
Apprentice
Joined: 08 Sep 2005 Posts: 40 Location: London
|
Hi
We have a file which is read by our file adapter which sends a sart-of-file message to the Q, and then each record of the file as a message, and then after the last message is sent, a end-of-file message is sent.
These messages are processed by a multi instanced flow. the delay is put in so that if the end-of-file message is recieved by the flow it will wait a set amount of time to ensure that its the last message processed by the flow
its a legacy piece of code. hope this explains the reasoning behind the time delay
williad |
|
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
|
|
|
|