aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes JMS Message Selectors Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS Message Selectors" Watch "JMS Message Selectors" New topic
Author

JMS Message Selectors

Colin Handy
Greenhorn

Joined: Jan 13, 2006
Posts: 6
If a JMS message sent to a local topic includes a message selector, will a remote MDB consumer of the message extract the complete message before filtering based upon the selector, or only extract the message header and properties? I need to limit my network bandwidth for certain consumers of messages (each message is only consumed by a single consumer), and I am trying to decide whether I can use a single topic or whether I need separate queues for each consumer. If I use a single topic, I don't want the message body delivered to each subscriber before the subscriber decides it does not want that message.
Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3704
    
    5

I think it varies depending on your server implementation and what you are using to filter messages. For example, in WebSphere you can use the WebSphere Message Broker or mediation queues that only read the header information and parse based on that rather than reading/parsing the entire message.


My Blog: Down Home Country Coding with Scott Selikoff
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: JMS Message Selectors