Continuous Queue Errors; Websphere Application Server - IBM BJ0NJML - Service And Asset Management Integration Manual

Continuous Queue Errors

WebSphere Application Server

Configuring the Error
Queue
JMS Queue Configuration
You can use different application server configurations to manage error messages.
When you are loading a large volume of messages, you can encounter a large
number of errors. The continuous queue continues to reprocess the messages at
the top of the queue that are in error instead of new messages that are being
added to the queue.
For example, you can run a nightly GL account update process that does not
complete successfully. The following day you find that the GL accounts are not in
the system and a high volume of system messages are generated. When a high
volume of messages occur, the queue processing continues to work on the same
messages and does not attempt to process new messages. You can avoid this
situation by using server-specific configurations for your queues.
You can configure a continuous queue to have a corresponding error queue. If a
message in the continuous queue encounters an error, the message is moved out
of the continuous queue to the error queue. The system moves the message when
the number of retries set in the maximum failed deliveries parameter is met. The
continuous queue then processes new queue messages.
To configure an error queue:
1
Configure an error queue destination within the same bus member where the
continuous queue resides.
2
Configure the continuous queue destination definition to have an exception
destination. The exception destination must point to the error queue
destination that you previously defined in step 1.
3
In the error queue add an exception destination that points to itself. Errors in
the error queue move from the top of the error queue to the bottom of the
error queue. Messages in error are continuously retried.
You must control how often the message reprocessing occurs to avoid excessive
system resource use. The integration framework message-driven bean
implementation provides an MDBDELAY property that delays the processing of
the messages, based on the property value.
When you configure the MDBDELAY property, the system retries the messages in
the error queue in a controlled manner. At some point, your message can be
successfully processed in a controlled environment.
Edit the ejb-jar.xml file to configure the message-driven bean delay. The default
value is 30 seconds (30000 milliseconds).
Continuous Queue
169