7 Replies Latest reply on Jul 4, 2013 8:15 AM by Will Tatam

    MDB pool-current-size stuck at 20 despite max-pool-size=50

    Will Tatam Newbie

      We have an MDB annocated with

       

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

       

      And have

       

      <strict-max-pool name="mdb-strict-max-pool" max-pool-size="50" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

       

      Yet the pool-current-size for this MDB never goes past 20. While I understand that maxSession is the limit of concurrent calls to onMessage on different MDBs we can't ever hit this value as the container (7.1.3) is only creating 20 instances and then stopping despite all the stats implying that it should be free to create more. What are we missing ?

       

      {

          "outcome" => "success",

          "result" => {

              "component-class-name" => "XXXXXXXMDB",

              "declared-roles" => [],

              "execution-time" => 0L,

              "invocations" => 0L,

              "peak-concurrent-invocations" => 0L,

              "pool-available-count" => 49,

              "pool-create-count" => 20,

              "pool-current-size" => 20,

              "pool-max-size" => 50,

              "pool-name" => "mdb-strict-max-pool",

              "pool-remove-count" => 0,

              "run-as-role" => undefined,

              "security-domain" => undefined,

              "timers" => [],

              "wait-time" => 0L

          }

      }