|
Problem(Abstract) |
The Publish or Subscribe application uses the default
broker queue, SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE. This queue is created
when Embedded Messaging is installed. By default, the backout threshold
property of this queue is set to 0. Therefore, the Embedded Messaging
component will never attempt to back out a bad message. This explains why
the message-driven bean Listener "Maximum Retries" limit is reached,
causing the Listener port to stop. |
|
|
|
Cause |
The default value of the Backout threshold property
for SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE is set to 0, and no
backout-requeue queue is defined for this queue. |
|
|
Resolving the
problem |
In order to set the backout threshold for the queue,
SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE
perform the following steps:
- From a command line, change to the directory:
embedded_messaging_root\bin
- Start the Embedded Messaging queue manager, by entering the command:
strmqm WAS_localhost_server1
- Enter the following command,
runmqsc WAS_localhost_server1
to enter the Embedded Messaging scripting client.
- To change the Backout threshold property to a value of
5, enter the following command:
ALTER QLOCAL(SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE)
BOTHRESH(5)
- To specify the Backout Requeue name (where messages will be
stored once the backout threshold limit has been reached) enter,
ALTER QLOCAL(SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE)
BOQNAME(qname)
where qname is the name of the backout queue and it is
required.
- To verify the settings have been correctly changed, enter the command:
DISPLAY Q(SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE)
- Exit from runmqsc by entering the command:
END
Note: Maximum Retries should be greater than the
Backout threshold property. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|