Messages sent to a queue during a performance test on TIBCO Enterprise Message Service (EMS) server do not expire, even if the expiration is set to the queue.

Messages sent to a queue during a performance test on TIBCO Enterprise Message Service (EMS) server do not expire, even if the expiration is set to the queue.

book

Article ID: KB0089905

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:

Description:
-----------------

1). Create a queue “queue.sample” and set the expiration to 5 seconds.
2). Send 100 messages to the queue using tibjmsMsgProducerPerf sample.
3). After 5 seconds the messages will not expire.

Environment:
------------------

TIBCO Enterprise Message Service – 5.x+
All OSPlatforms

Symptoms:
--------------

Messages are not expired even after the expiration set on the queue has elapsed.

Cause:
------------------

In the “perf” samples shipped with EMS, the setting of TimeStamp has been disabled by design for minimalistic message creation. If the setting of JMSTimeStamp is disabled, though expiration is set at the destination level the messages will never expire. This is  because the EMS server will not be able to compare the TimeStamp of the message with the current system time before expiring them.

Resolution:
------------------

Modify the perf application to set JMSTimeStamp or test the expiration using tibjmsQueeuSender application instead.

Issue/Introduction

Messages sent to a queue during a performance test on TIBCO Enterprise Message Service (EMS) server do not expire, even if the expiration is set to the queue.