MQSeries.net :: View topic - Expiration 36000 is set but message expires immediately !!

mansul · Posted: Sun Mar 16, 2003 9:58 pm Post subject:

We need your help on a problem related to expiration of messages. This is our observation so far.

Environment:
Platform
2064-1CG (6 way - 1092 mips)
WMQI LPAR: Two processors allocated (capped to 18Mips) + 1.2 GB
memory
SOFTWARE
OS/390 V2.10
DB2 7.1
MQ 5.2
MQWF 3.3.0
WMQI V2.1 CSD 3
Java 1.3.1 hm131s-20020207

The MQSI Broker on S/390 puts messages into a remote queue which points to a local queue on the Sun Solaris machine. There is a trace file (out.txt) wired to the output node of the message flow. The trace file is generated when a message is successfully put into the remote queue.

For the past few days, messages have been intermittently “lost”. The out.txt trace file is generated but
a. message does not arrive at the local queue on the Sun Solaris machine
b. channel count on the S/390 machine does not increase
c. no messages found in the Sun Solaris SYSTEM.DEAD.LETTER.DEAD

The system log on the S/390 machine does not show any errors. There are no messages put into the S/390 SYSTEM.DEAD.LETTER.QUEUE. Also, there are no error messages found in the AMQERR(n).LOG on the Sun Solaris machine.

The channel between the S/390 machine & Sun Solaris machine is never stopped. Messages go “missing’ at random. Out of 10 messages, only 3 are sent across to the Sun Solaris machine.

The messages which go “missing” are
a. non-persistent
b. has expiry set to 36000

We are setting an expiry of one hour. (Set OutputRoot.MQMD.Expiry = 36000) in the last compute node just before the MQOutput Node. We also have a trace connected to output terminal of this mq out put node, which shows the Expiry being set to 36000. This output queue is a remote queue pointing to a queue on E-point (Sun Solaris box).

Most of the cases, these messages reach the Sun box, (For testing another mq output node(an NT test q has been connected to this again). and we see the messages to have an expiry of around one hour left when it reaches the remote queues.

We are testing with the same transaction, with the same data each time, and once in a while, roughly once in 10 times, it so happens that the messages seem to expire almost immediately, even though the trace file still shows the expiry set to 36000.

We have put the report option for Expiration with data and in the above cases when it expires immediately, we get the expiration report almost immediately.

We are unable to find out if this behaviour is due to the queue manager and mq? or does it have anything to do with our flows?
_________________
Roy