Change Notes item #815941, was opened at 2003-10-01 15:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=815941&group_id=22866
Category: JBossMQ
Group: v3.2
Status: Open
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: Maximum depth of queues and subscriptions
Initial Comment:
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
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=815941&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
