1 Reply Latest reply on Jun 16, 2009 7:55 PM by Clebert Suconic

    MDB Throttling:

    Jeremy Norris Newbie

      What is the best way to throttle MDB consumers?

      There is @Pool (eg: JBoss 5.1.x):

      @Pool(value = PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX, maxSize = n)
      


      And, "maxSession":

      @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "n")
      


      How are these two settings related? Which setting is more portable (if any)?
      (Incidentally, in JBoss 5.1.x, neither of these settings appear to limit the number of concurrent consumers for an MDB).

      Also, is there any way to throttle the MDB consumers automatically based on CPU or IO activity and available resources?

      What are the best practices here?



        • 1. Re: MDB Throttling:
          Clebert Suconic Master

          MDB itself is part of EJB3, not JMS.

          ActivactionConfigProperty belongs to the JCA adapter. So it's better to ask on the JCA forum.


          Also, is there any way to throttle the MDB consumers automatically based on CPU or IO activity and available resources?



          I will take that questions as a regular consumer.

          It shouldn't make any difference. You model your consumers based on your useCase (or business if you prefer calling it this way). A Messaging System should load balance messages accordingly to your resources anyway.