ConfigQueue

Version 26

Created by adrianbrock on Apr 10, 2004 11:07 PM. Last modified by siofumbar on Sep 28, 2007 4:32 AM.

Queue Configuration

A permenant deployment of a Queue. You can find examples in deploy{-hasingleton}/jms/jbossmq-destinations-service.xml

These examples are used by the JBoss testsuite and can safely be removed.

There is nothing special about the name of the -service.xml where the queue is deployed; it could for

example be placed in a myapp-service.xml inside your mdb jar.

Example Configuration

  <mbean code="org.jboss.mq.server.jmx.Queue"
      name="jboss.mq.destination:service=Queue,name=testQueue">
    <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
    <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
    <attribute name="SecurityConf">
      <security>
        <role name="guest" read="true" write="true"></role>
        <role name="publisher" read="true" write="true" create="false"></role>
        <role name="noacc" read="false" write="false" create="false"></role>
      </security>
    </attribute>
  </mbean>

Configurable Attributes

```
DestinationManager
```
- the object name of the DestinationManager where the queue is deployed
```
SecurityManager
```
- the object name of the SecurityManager where the SecurityConf is deployed
```
SecurityConf
```
- the configuration interpreted by the SecurityManager
```
JNDIName
```
- the jndi binding of the Queue, it looks for a jmx attribute "name" in the Queue's object name when none is specified
```
MaxDepth
```
- the maximum depth of the Queue
```
InMemory
```
- don't persist messages and avoid message softening when using the NullPersistenceManager
```
RedeliveryLimit
```
- the maximum times a message is nacked before a message is sent to the DLQ (0 - don't redeliver, n - redeliver n times - see (2) )
```
RedeliveryDelay
```
- the length of time in milli-seconds to wait before a message is redelivered after a nack
```
MessageCounterHistoryDayLimit
```
- the number of days to keep MessageCounter history
```
ReceiversImpl
```
- the class to use for the receivers implementation (from JBoss-3.2.4)
```
RecoveryRetries
```
- the recovery retries for the queue - default 0 - zero(from JBoss-4.0.3). Specifies the number of times uncommitted transactions are to be resolved before failing.
ExpiryDestination

Informational

```
MessageCounter
```
- the MessageCounter for this Queue
```
QueueDepth
```
- the number of undelivered messages in the queue
```
ScheduledMessageCount
```
- the number of messages waiting to be scheduled
```
ReceiversCount
```
- the number of ClientConsumers waiting for a message
```
SubscribersCount
```
- the number of ClientConsumers subscribed to the queue but not necessarily waiting for a message
```
InProcessMessageCount
```
- the number of messages received by clients but not acknowledged (from 4.0.5)

Operations

```
removeAllMessages
```
- clears the queue
```
resetMessageCounter
```
- clear the MessageCounter data for this queue
```
resetMessageCounterHistory
```
- clear the MessageCounter history data for this queue
```
listMessages()
```
- list the messages in the queue (1 - from 3.2.4)
```
listMessages(String selector)
```
- list the messages in the queue with an optional selector (1 - from 3.2.4)
```
listScheduledMessages()
```
- list the scheduled messages in the queue (1 - from 4.0.5)
```
listScheduledMessages(String selector)
```
- list the scheduled messages in the queue with an optional selector (1 - from 4.0.5)
```
listInProcessMessages()
```
- list the unacknowledged messages in the queue (1 - from 4.0.5)
```
listInProcessMessages(String selector)
```
- list the unacknowledged messages in the queue with an optional selector (1 - from 4.0.5)
```
listReceivers
```
- list the ClientConsumers waiting to receive a message
```
listSubscribers
```
- list the ClientConsumers subscribed to the queue but not necessarily waiting for a message

Notes

(1) Use with care when the queue is very full, there is no paging, the entire queue will be displayed which could cause an OutOfMemory
(2) Somebody keeps changing this to say -1 is redeliver forever. The
```
RedeliveryLimit
```
is only handled by the MDB. If you are not using the MDB, then it is always redeliver forever, unless you check this property yourself against the redelivered count property in your own client. -1 (really not defined - the default) means use the configuration on the MDB NOT redeliver forever.

JBossDeveloper