WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Troubleshooting using queues

Queues can be used for troubleshooting because they usually process and go to zero quickly. If any of the queues are not zero, it indicates a problem. WebSphere® Premises Server uses WebSphere MQ queues and WebSphere Application Server SIBus queues.

WebSphere Application Server SIBus queues

You can view all of the queues, including the SIBus queues, by navigating to Resources > JMS > Queues in the WebSphere Application Server administrative console.

ALE.Report.Bus.Queue
JNDI name is jms/ale.report.bus.q. This SIBus queue is used by the Application Level Events (ALE) engine to put reports that are generated by ALE into the system.
EVENT.MONITOR.QUEUE
JNDI name is jms/event.monitor.q. This SIBus queue monitors events as they occur in real-time.
Enterprise.In.Bus.Queue
JNDI name is jms/enterprise.in.bus.q. Enterprise applications send messages to this queue.
Enterprise.Out.Bus.Queue
JNDI name is jms/enterprise.out.bus.q. Messages are sent to this queue from WebSphere Premises Server to be processed by enterprise applications.

WebSphere MQ queues

WebSphere MQ queues for WebSphere Premises Server are named from the premises server point-of-view. "IN" queues are coming "in" to WebSphere Premises Server. "OUT" queues are going "out" from WebSphere Premises Server to the MicroBroker (for the Data Capture and Delivery controller) and the back-end adapters.

Tip: For an advanced troubleshooting technique, you can stop individual queues from processing to help isolate where the problem is occurring.

Queues in IBM.DC.QM

DC.IN.Q
This queue receives messages from Data Capture and Delivery and sends them to the sensor gateway to publish to the SIBus.
DC.OUT.Q
Messages flow from message-driven beans (MDBs) through this queue to the Data Capture and Delivery controllers.
DEAD.MESSAGE.Q
This queue keeps messages that cannot be processed due to some internal error. IBM® Support may ask administrators to report the contents of this queue when troubleshooting a problem.
ENTERPRISE.IN.Q
Enterprise applications send messages to the ENTERPRISE.IN.Q queue, where they are sent to the SIBus.
ENTERPRISE.OUT.Q
Messages are sent to the ENTERPRISE.OUT.Q queue from WebSphere Premises Server to be processed by enterprise applications.
fmb.sync.q
An internal queue used for communication.

Queues in IBM.RFID.QM

ALE.REPORT.Q
This queue is used by the Application Level Events (ALE) engine to put reports that are generated by ALE into the system.
ALE.TAG.INPUT.Q
The ALE engine uses this queue to retrieve tag read events so that it can filter them.
CONTROL.IN.Q
Messages come to the CONTROL.IN.Q queue from adapters and are processed into task messages and sent to the TASK.Q queue.
CONTROL.OUT.Q
Messages come to the CONTROL.OUT.Q queue from the TASK.Q queue and are sent to the appropriate adapters for implementation.
DEAD.MESSAGE.Q
This queue keeps messages that cannot be processed due to some internal error. IBM Support may ask administrators to report the contents of this queue when troubleshooting a problem.
EDGE.IN.Q
Messages flow from the MicroBroker bridge into the EDGE.IN.Q queue. They can be command, event, or tag messages. The messages are processed into task messages and sent to the TASK.Q queue.
EDGE.OUT.Q
Task messages are sent from the TASK.Q queue to the EDGE.OUT.Q queue where they are converted into MicroBroker messages and sent to the edge controller.
EDGE.OUTBYTES.Q
This queue is used to send serialized objects instead of XML to the edge controller. It requires no transforms. It is used by WebSphere Premises Server to send print jobs to the edge controller.
EDGE.PRINT.IN.Q
This queue is a status queue that is used to get the status of a print job.
fmb.sync.q
An internal queue used for communication.
KIMONO.RESPONSE.Q
This queue gets a response to an event from the back end.
MANAGEMENT.Q
This queue processes messages specific to system management, such heartbeats and alerts.
PERSISTENCE.Q
This queue processes tag persistence messages when tag persistence is enabled in the SystemAgent.
TAGMONITOR.OUT.Q
This queue monitors tag reads as they occur in real-time.
TASK.Q
Messages come to the TASK.Q queue from the EDGE.IN.Q queue and are sent to the CONTROL.OUT.Q queue. Messages also come to the TASK.Q queue from the CONTROL.IN.Q queue and are sent to the EDGE.OUT.Q queue.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.