Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-4805

In strict-max-bean-instance-pool derive-size and max-pool-size should be alternatives

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR14
    • 7.0.0.GA, 7.1.0.DR15
    • EJB, User Experience
    • None 

      /subsystem=ejb3/strict-max-bean-instance-pool=test-pool:add(derive-size=none, max-pool-size=30L, timeout=8L, timeout-unit=SECONDS)
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0105: max-pool-size is invalid in combination with derive-size",
    "rolled-back" => true
}

/subsystem=ejb3/strict-max-bean-instance-pool=test-pool:add(max-pool-size=30L, timeout=8L, timeout-unit=SECONDS)
{"outcome" => "success"}

/subsystem=ejb3/strict-max-bean-instance-pool=test-pool:read-attribute(name=derive-size)
{
    "outcome" => "success",
    "result" => "none"
}

      This is caused by max-pool-size and derive-size being declared as alternatives although this is not entirely true.

              bstansbe@redhat.com Brian Stansberry
              pjelinek@redhat.com Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: