| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timeoutnotification node and expiry |
« View previous topic :: View next topic » |
| Author |
Message
|
| wbi_telecom |
 Posted: Wed Dec 17, 2008 2:55 pm Post subject: Timeoutnotification node and expiry |
 |
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
version 6.0.2 on Z-Linux
I am working on a flow that sends a heartbeat message to various mainframe regions to see if they are up and running . The flow starts with a TimeoutNotificaiton node and in subsequent compute node I create a MQMD in ESQL. Everything works fine except when I put Expiry in MQMD, I cannot see the message on the Queue regardless the value I put. I set a very high value of expiry but still the same result. I checked the value of Expiration Time under Properties and that it contains the same value I am setting in Expiry.
I stopped the message in Debugger and then manually changed the value of Expiry and then resumed the debugger , the message was on the queue with the value that I put manually in Debugger but it does not work when I set it using ESQL.
Has anyone seen this behavior?
Cheers, |
|
| Back to top |
|
 |
| wbi_telecom |
| Posted: Thu Dec 18, 2008 5:50 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
Here is the Trace I got just before MQOutput. It shows the Expiry correctly under MQMD and Properties.
(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 0
(0x03000000):Transactional = TRUE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = NULL
(0x03000000):ExpirationTime = 600
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = ''
(0x03000000):Topic = NULL
(0x03000000):ContentType = ''
)
(0x01000000):MQMD = (
(0x03000000):StrucId = 'MD '
(0x03000000):Version = 2
(0x03000000):MsgType = 8
(0x03000000):Format = 'MQSTR '
(0x03000000):Expiry = 600
(0x03000000):CorrelId = X'000000000000000000000000000000000000000000000000'
)
(0x01000010):XMLNS = (
(0x01000000):TimeoutRequest = (
(0x01000000):Action = (
(0x02000000): = 'SET'
)
(0x01000000):Identifier = (
(0x02000000): = 'SampleAuto'
)
(0x01000000):StartDate = (
(0x02000000): = '2008-12-18'
)
(0x01000000):StartTime = (
(0x02000000): = '08:46:23.081064'
)
(0x01000000):Count = (
(0x02000000): = 1
)
(0x01000000):Interval = (
(0x02000000): = 10
)
(0x01000000):IgnoreMissed = (
(0x02000000): = TRUE
)
(0x01000000):AllowOverwrite = (
(0x02000000): = TRUE
)
)
)
) |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Thu Dec 18, 2008 10:32 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
Some more tests have revealed that this node works in such a way that all the message generated from this node are set to expire at the same time on the queue . So if I set the expiry at a very high number, I am able to see messages on the queue but then subsequent messages have less "time to live" on the queue than the earlier message.
I am not sure if this is done by design. I want all the messages to have the same expiry i.e. same "time to live" on the queue. I will open a PMR and see if I get anything out of it
Cheers, |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Sun Dec 21, 2008 11:47 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
yes, I have seen the same...if you search on the forum on expiry etc, you will find that I gave a detail explanation.
One way to get past this problem is to let the flow that set the expiry be started from MQInput node. If the flow is started from HTTP or timer nodes the expiry does not work...I presume it is a bug.
So, my solution is to do the timer nodes, but that will only put a dummy message into an input queue for another flow. That flow will create the msg with the expiry value in it.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| 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
|
|
|
|
