| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Does the Broker alter the message's Expiry |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Wed Jan 30, 2008 1:34 pm Post subject: Does the Broker alter the message's Expiry |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Windows 2003 SP1
MQ 6.0.2.1
WB-IMB 5.0.4
Our MQ API exit is showing that a message flow is changing the Expiry. We see it 10,000,000 on the MQGET, but after the flow has done its thing the MQPUT shows the Expiry altered, sometimes increased (?!) by a tenth of a second, sometimes decreased, other times not altered at all.
Some examples:
API----------TimeStamp----------Expiry
MQGET 15:04:53.956000 10000000
MQPUT 15:04:54.018000 10000001 ?!?!
MQGET 15:04:14.165000 10000000
MQPUT 15:04:14.228000 10000001 ?!?!
MQGET 15:04:14.775000 10000000
MQPUT 15:04:15.946000 9999989
The developers have stated that their code does not touch expiry and I agree. We looked at the ESQL together. Expiry is not being touched between the input message and the output message.
| Code: |
CREATE FUNCTION main() RETURNS BOOLEAN BEGIN
DECLARE I INTEGER;
SET I = 1;
WHILE I < CARDINALITY(InputRoot.*[]) DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I=I+1;
END WHILE; |
I do see where they are setting the MQMD's Reply To Q info. No other code to modify the MQMD of the output message.
(The flow does put some routing info to a HOLD queue to be used by the MQGET node in the reply flow, and that hold message only does get its expiry set to 1,728,000).
Does the Broker consider how long a message spends inside a message flow and makes an attempt to have expiry reflect that? I couldn't find anything in the WB-IMB Info Center.
How / why would the Expiry be upped by a tenth of a second?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 30, 2008 1:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you look for APARS for WMB v5 for fixes that may be included in newer FPs than FP4?
There are six newer FPs than FP 4, after all...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 30, 2008 1:52 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
There are a couple of fixes for Expiry with Aggregation and Timeout nodes. I don't use those.
For a relativily basic flow, does the Broker consider Expiry and possibly change it if the processing in the flow takes more than a tenth of a second? It seems to be happening but I can't find documentation on this feature.
(We're going to WMB 6.1 in a few months as soon as the new servers get here. I'm not upgrading to 5.0.10.)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Jan 30, 2008 7:08 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I know that base WMQ changes the expiry as a message moves through the system:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzak.doc/js01159.htm
However, I would have thought that the broker was more of an application program rather than a WMQ system program. The link above does state:
| Quote: |
| Likewise, an application forwarding this message to another queue might decrement the value if necessary, if it has retained the message for a significant time. However, the expiration time is treated as approximate, and the value need not be decremented to reflect small time intervals. |
You may have to wait for a broker developer to arrive in the morning to get a definitive answer. |
|
| 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
|
|
|
|
