JMS consumers and MDBs in free pool

Question

          Hello
          I am using WLS 7.0 SP1. I notice the following when using MDBs listening on
          a JMS queue.
          The WLS console shows the number of JMS consumers to be equal to the <max-free-beans-in-pool>
          parameter value in the MDBs deployment descriptor. I would expect the number of
          JMS consumers to be equal to the <initial-free-beans-in-pool> value before I start
          posting messages to the queue.
          Thanks
          Ramdas
          

Answer 1

Hi Ramdas,
          I'm fairly sure that this is long-standing behavior, that
          also occurs in 6.1 and 8.1. Since the number of beans
          is limited by the number of available threads, the fact
          that all of them are allocated right away is usually not
          an issue.
          Post to the ejb newsgroup to make sure.
          Tom
          P.S. If you haven't already, I suggest reading
          the most recent version of the JMS performance guide. It
          contains info on tuning MDB threading and pooling. You
          can find the guide on dev2dev.
          Ramdas Hegde wrote:
          > Hello
          >
          > I am using WLS 7.0 SP1. I notice the following when using MDBs listening on
          > a JMS queue.
          > The WLS console shows the number of JMS consumers to be equal to the <max-free-beans-in-pool>
          > parameter value in the MDBs deployment descriptor. I would expect the number of
          > JMS consumers to be equal to the <initial-free-beans-in-pool> value before I start
          > posting messages to the queue.
          >
          > Thanks
          >
          > Ramdas