| Author |
Message
|
| Heidils |
 Posted: Thu Jul 10, 2003 4:28 am Post subject: Message Expiry |
 |
|
Novice
Joined: 25 May 2003
Posts: 11
Location: SA
|
We are using WMQI 2.1 for our message flows and are getting various messages from a 3rd party with an expiry time of 65 seconds on a generic input queue. This expiry time is only required for messages coming into the system (SLA) but it seems that we are 'loosing' the response messages due to this expiry time set.
I have added a compute node in the flow just before the output node with the code Set OutputRoot.MQMD.Expiry = -1 This seems to be working but what I would like to know is, is the right place to do this? Is there a better place or way to do this?
Also what would happen to a message with an expiry time set, of say 60 seconds, and where the message flow / processing of the message takes longer than the set expiry time. Is it possible that this message could be lost or does the expiry time only apply to the GET of the message from the queue.
Thanks!!!
 |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Jul 10, 2003 6:19 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| I assume these messages are 'requests' for information? and the expiry is set to 65 seconds and after that the requestor is no longer interested in the reply? Otherwise why set the expiry in the first place... or why would you reset the expiry to make sure the 'answer' gets back ? |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 10, 2003 5:46 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Since you were not changing the expiry time on the reply messages before, your messages were getting lost (expired).
Yes, Compute node is the right place to reset the expiry time. I'd suggest you set some expiry time on the reply messages also. This will help in clearing the reply queue automatically if the client application is not available for receiving the reply messages. It would also depend on the type of reply messages. For critical reply messages, you would want to set unlimited expiry time.
I think the expiry time is applicable only when doing the MQGET and not while processing the message. Pls Correct me if I am wrong.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Heidils |
| Posted: Thu Jul 10, 2003 10:24 pm Post subject: |
|
|
Novice
Joined: 25 May 2003
Posts: 11
Location: SA
|
Thanks guys!
To clear up the expiry - we are doing real time processing of claims. Because of the nature of the business the providers does not want to wait for more than a minute for an answer and would rather send the request again. On the other hand if they are not available they still want the answer once we've processed the claim. Sounds mixed up but that's the business!!! 
I'll let you know if we pick up problems with message expirying while we are processing but so far so good...  |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Jul 10, 2003 11:04 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
hey that sounds familiar...  I have heared requirements like that (also from Claim 'processors') of responses within seconds ... must be nerv wrecking business |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Jul 11, 2003 6:16 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Is application that is processing the request just copying the mqmd from
the request into the response ????
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
