This documentation is for WSO2 Message Broker version 2.0.1. View documentation for the latest release.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

The WSO2 MB management console provides capability to create, manage and delete queues through a simplified UI. Users can perform the following management operations.

The following information is also available in this section:

Add Queues 

1. Log in to the management console and select "Queues -> Add" menu from the "Main" menu.


2.  The "Add Queue" window opens. Provide the name of the queue and click the "Add Queue" button.

Queue Name is the identifier of the queue you have created. Added queues get created in the Message Broker server, ready to receive messages and send messages to client applications. 

Note

A meaningful name should be given as the queue name without any "/" literals, and the name should not begin with character sequence "tmp_" as it is used by the broker for internal purposes.

3. If the queue is created successfully, a message will appear. 

Note

External applications can create queues pragmatically as well.

Browse Queues 

4.  Once a queue is added, the user is directed to "Queue List" window where the newly-added queue will be listed.

The table shows all the queues available in message broker server, along with message count of each queue, number of messages in persistent state not delivered to the consuming client. Queues created by external client applications will be listed here with message count in the same way. But, in order to view them you should be in "Super Tenant" (default) mode. 

Tenant-Specific Queues

When a queue is created from a tenant other than the super tenant, the created queue will have the tenant domain appended to the name of the queue. For example, if the tenant domain is "a.com", when the queue is created with the name "myQueue", the queue name will be displayed in the "Queue List" window as "a.com/myQueue". For example,

According to this example, if the user intends to send to and consume from the queue using an external client application, the queue name that should be used is "a.com/myQueue". Also, if a user needs to create a queue called "myQueue" using an external JMS client under tenant domain "a.com", the queue name should be "a.com/myQueue".

Delete Queues 

5. To delete a queue, simply click the "Delete" link associated with the queue. Users can delete one or more queues from the server.


When a queue is deleted, all the messages persisted with that queue is removed. A "deletion successful" message pops-up on successful queue deletion. Deletion can be verified by looking at the available queue list.

Distributed Queues in Clustered Mode

When few instances of WSO2 Message Broker are running, queues are always distributed. At a particular moment, a queue is owned by some node in the cluster. When a node fails and client applications are configured to use "fail-over", it will be able to send and consume messages from the cluster without any failures or message loses. Clustering operations and synchronizing messages across the cluster is fully transparent to the user.

Advanced Queue Configurations

When setting up an instance of WSO2 Message Broker, there are various advanced queue configurations that can be done to improve performance and functionality. For information, refer to section Message Broker Advanced Configurations.

  • No labels