[jboss-jira] [JBoss JIRA] Closed: (JBAS-1348) Message Selector Performance

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-1348?page=all ]

Adrian Brock closed JBAS-1348.
------------------------------

    Resolution: Deferred

Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING

If anybody wants to provide a patch that implements these,
the issue can be reopened.

Duplicates of these issues will be closed
unless they provide an implementation/patch.

Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.

> Message Selector Performance
> ----------------------------
>
>                 Key: JBAS-1348
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1348
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
>            Reporter: Adrian Brock
>            Priority: Minor
>
> Improving Message Selector Performance
> It is a common anti-pattern for users to set up a contested queue
> where multiple receivers try to take messages based on a message selector.
> In most circumstances a Topic is what they should be using.
> But there is a circumstance where a Topic does not work as required,
> that is when a message matches many of the receiver's selector but you
> only want one receiver to process the message (it doesn't matter which).
> The problem is that when a receiver does not match a message towards
> the top of a large Queue (or none at all). The operation to find a message
> or discover there are no messages is very expensive. It is read and skip.
> This can be even worse when the bottom of the queue has been moved out
> to disk by the MessageCache.
> The solution is to provide "an index" over a particular property,
> e.g.
> <mbean code="org.jboss.mq.server.jmx.Queue"
> 	 name="jboss.mq.destination:service=Queue,name=A">
>     <optimized-selector>JMSMessageID</optimized-selector>
>     <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
> </mbean>
> This configuration should be passed via the BasicQueueParameters to the BasicQueue.
> NOTE: This is irrevelent for Topics. Topics run their selector before the message is added
> to the subscription, anything not matching the selector is dropped.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira