ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Message selectors and priorities

Post new topic  Reply to topic
 Message selectors and priorities « View previous topic :: View next topic » 
Author Message
sfari
PostPosted: Fri Dec 21, 2007 1:42 am    Post subject: Message selectors and priorities Reply with quote

Centurion

Joined: 15 Apr 2003
Posts: 144

Hi all,

We have a performance problem on an existing application. I am currently trying to find out what could be the reason.

This is the rough application design:

We have three different types of messages (type=A, type=B, type=C) on a queue. Three different Message Driven Beans are consuming them using message selectors. The application designer decided that messages of type=A have the biggest priority=5, B has 4, and C has 3.

The message driven beans are all running in the same application server. On the queue I can see that there is only one connection open for browse and 3 for each MDB for input.

It seems that if messages with priority=5 (type=A) are constantly arriving it does slow down the consumption of the lower priority messages.

Does somebody know how the selecting mechanism with this only one connection for all three different selectors is exactly working? Is my assumption possible or does it sound absurd? How does priority influence selectors?

Thanks for any help!
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Dec 21, 2007 3:29 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

A classic example of why you don't want to share queues...

You're likely using one single ListenerPort for the queue, assigned to all three MDBs. This ListenerPort can only get one message at a time, and start one MDB instance. If it spends it spends all it's time starting messages of Type A, then it can't start the MDBs for Type B or C.

Also, using selectors on anything other than MsgID or correlationID is going to be slow!

Much better to either use three queues, or one MDB that doesn't use a selector and calls three session beans based on message type (a dispatcher pattern).
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
bower5932
PostPosted: Fri Dec 21, 2007 4:53 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

There are a couple of articles on developerWorks that shed some light on what is going on with MDBs receiving messages. You might want to check them out:

http://www.ibm.com/developerworks/websphere/library/techarticles/0503_bhasin/0503_bhasin.html
http://www.ibm.com/developerworks/websphere/library/techarticles/0611_titheridge/0611_titheridge.html
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Message selectors and priorities
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.