Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-6395

EJB2 CMP - no entity-bean instance pool configured in *full* profiles with cmp

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 7.1.3.Final (EAP)
    • EJB
    • Workaround Exists
    • Hide

      The configuration can be added if needed:

      <subsystem xmlns="urn:jboss:domain:ejb3:1.4">
      ...
      <entity-bean>
      <bean-instance-pool-ref pool-name="entity-strict-max-pool"/>
      </entity-bean>
      <pools>
      <bean-instance-pools>
      ...
      <strict-max-pool name="entity-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>
      </bean-instance-pools>
      </pools>

      Show
      The configuration can be added if needed: <subsystem xmlns="urn:jboss:domain:ejb3:1.4"> ... <entity-bean> <bean-instance-pool-ref pool-name="entity-strict-max-pool"/> </entity-bean> <pools> <bean-instance-pools> ... <strict-max-pool name="entity-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> </bean-instance-pools> </pools>
    • Low

      The ejb3 subsystem does not configure entity-bean.bean-instance-pool.
      In that case the CMP subsystem must create a instance for each entity if it is used.
      This might be a performance issue (instantiation and GC), also the setContext/unsetContext methods must be called.

              rhn-support-wfink Wolf Fink
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: