5.7.2. Configuring Queues
184.108.40.206. Queue MBean Attributes
- Defines the queue name.
- Defines the JNDI name that binds the queue.
- Defines the DLQ (Dead Letter Queue) for this queue and overrides any value set in the Server Peer configuration file.
- Defines the expiry queue and overrides any value set in the Server Peer configuration file.
- Defines the redelivery delay to be applied to this queue and overrides any value set in the Server Peer configuration file.
- Defines the maximum number of times message delivery is attempted before the message is sent to the DLQ, if configured. The default value,
-1, means that the value from the Server Peer configuration file is used. Any other setting will override the value set in the Server Peer configuration file.
trueif the queue was created programmatically.
- Returns the total number of messages in the queue. That is, the number of messages being scheduled plus the number being delivered, plus the number not being delivered.
- Returns the number of scheduled messages in the queue. This is the number of messages scheduled to be delivered at a later date.Scheduled delivery lets you specify the earliest time at which a particular message will be delivered. For example, you can send a message now, and specify that it will not be delivered for two hours. To do so, set the following in the message header:
long now = System.currentTimeMillis(); Message msg = sess.createMessage(); msg.setLongProperty(JBossMessage.JMS_JBOSS_SCHEDULED_DELIVERY_PROP_NAME, now + 1000 * 60 * 60 * 2); prod.send(msg);
- Specifies the maximum number of messages that can be held in a queue. Any excess messages will be dropped. The default value is
-1, which is unbounded.
- This attribute must be set to
trueif the destination is clustered.
- Each queue maintains a message counter.
- The statistics for the message counter.
- The maximum number of days for which to hold message counter history. Overrides any value set in the Server Peer configuration file.
- The number of consumers currently consuming from the queue.
- Specifies how queue services with clustered attributes that differ from previously deployed attributes are handled. If set to
true, all remaining messages in the queue are deleted after the queue service re-deployment if the queue service attribute contains a different clustered attribute. If set to
false(default), all messages are reserved.
true, and add the queue service configuration to each node.
falsein one of the queue configurations and delete all other queues in the cluster.
220.127.116.11.1. Destination Security Configuration
<SecurityConfig> <security> <role read="true" write="true" create="true"/> </security> <SecurityConfig>
- Specifies the role can create consumers, receive messages, and browse the destination.
- Specifies the role can create producers, or send messages to the destination.
- Specifies the role can create durable subscriptions on this destination.
SecurityConfigelement is not specified, then the default security configuration from the Server Peer will be used instead.
18.104.22.168.2. Destination paging parameters
- Specifies the maximum number of messages held by the queue or topic subscription in memory at any one time. The actual queue can hold more messages, but these are paged to and from storage as messages are added or consumed. If no value is specified, the default is
- Specifies the maximum number of messages that are pre-loaded per operation when loading messages from the queue or subscription. If no value is specified, the default is
- Specifies the maximum number of messages the Down Cache holds before the messages are flushed to storage. The default value is
2000messages.When messages are paged to storage from the queue, they enter a Down Cache before being written to storage. This enables the write to occur as a single operation, which aids performance.
NotePaging parameters for temporary queues must be specified on the appropriate connection factory. Refer to Section 5.8, “Configuring Connection Factories” for detailed information about the different connection factories available.
22.214.171.124.3. Queue Managed Bean Operations
- Removes (and deletes) all messages from the queue.
ImportantThis will permanently delete all messages from the queue; use this operation with caution.
- Lists all messages currently in the queue. Using a JMS selector as an argument in this operation lets you retrieve a subset of the messages in the queue that match the given criteria.
- Lists all durable messages in the queue. Using a JMS selector as an argument in this operation lets you retrieve a subset of messages in the queue that match the given criteria.
- Lists all non-durable messages in a queue. Using a JMS selector as an argument in this operation lets you retrieve a subset of messages in the queue that match the given criteria.
- Resets the message counter to zero.
- Resets the message counter history.
- Lists the message counter in HTML format.
- Lists the message counter history in HTML format.