Browse Prior Art Database

Discarding messages sent to temporary destinations on remote queue managers

IP.com Disclosure Number: IPCOM000201080D
Publication Date: 2010-Nov-08
Document File: 2 page(s) / 196K

Publishing Venue

The IP.com Prior Art Database

Abstract

Automatically discarding electronic messages addressed to non-existent destinations

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 01 of 2

Discarding messages sent to temporary destinations on remote queue managers

Introduction

The solution describes a way for messages that are addressed to destinations which do not exist (or more specifically, because they no longer exist) can be safely discarded if the sending application deems it appropriate.

    The solution can be used to prevent the unnecessary build up of 'dead letter' messages in an environment where the destination no long exists. This is a common situation in a messaging environment where temporary destinations are used to send messages between applications.

The terminology in the article refers to artifacts common in a messaging environment:

     - Queue Manager - A computer process which manages the flow of messages from applications to queues, or other queue managers
- Queue - A repository of messages which can be read and deleted by applications
- Transmit Queue - A repository of messages which are to be transferred from one queue manager to another

     - Dead Letter Queue - A repository of messages which cannot be delivered to their destination

    In a remote queueing environment, a message can be sent to a queue on a queue manager via an intermediate queue manager (see diagram below).

    In such an environment, the message (step 1 in the diagram) is placed on the transmit queue of the intermediate queue manager (step 2), and is sent over a message channel to the destination queue manager (step 3).

    As this happens, it is not known whether the queue exists on the destination queue manager.

    When the message arrives at the destination queue manager, if the queue does not exist, the message is placed on the dead letter queue (step 4) for that queue manager (if one has been specified).

(This page contains 00 pictures or other non-text object)

This scenario has a drawback.

If the message is being sent in response to an original request coming from


Page 02 of 2

an application connected to the remote QM, the destination queue for...