#263 Maximum depth of queues and subscriptions

v3.2
open
nobody
JBossMQ (8)
5
2003-10-01
2003-10-01
Adrian Brock
No

The maximum depth of queues and individual topic
subscriptions
can be configured. See the following example:

<mbean code="org.jboss.mq.server.jmx.Queue"
name="jboss.mq.destination:service=Queue,name=A">
<depends
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
<attribute name="MaxDepth">100</attribute>
</mbean>

The max depth can still be exeeded in a number of
situations,
e.g. when a message is knacked back into the queue.

Also transactions perform read committed processing,
they look at the current size of queue, ignoring any
messages
that may be added as a result of the current transaction or
other transactions.
This is because we don't want the transaction to fail
during
the commit phase when the message is physically added
to the queue.

Regards,
Adrian

Discussion

  • Adrian Brock
    Adrian Brock
    2003-10-01

    Logged In: YES
    user_id=9459

    Additionally the maximum depth can be set globally for
    temporary topics and queues.

    example:

    <mbean code="org.jboss.mq.server.jmx.DestinationManager"
    name="jboss.mq:service=DestinationManager">
    <depends
    optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
    <depends
    optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
    <depends
    optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
    <attribute name="TemporaryMaxDepth">100</attribute>
    </mbean>